CVE-2023-44184

Junos OS and Junos OS Evolved: High CPU load due to specific NETCONF command

MEDIUM

6.5

CVSS Score

Published: October 12, 2023 at 11:02 PM UTC

Updated: June 17, 2026 at 06:27 AM UTC

3 products affected across 2 vendorsJunosJunos OS EvolvedJunos OS Evolved

Using Junos OS by Juniper Networks?

Get instant alerts when new vulnerabilities affect Junos OS - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM6.5

Exploit prediction

EPSS 0.6%

SSVC

No known exploit

Description

An Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in the management daemon (mgd) process of Juniper Networks Junos OS and Junos OS Evolved allows a network-based authenticated low-privileged attacker, by executing a specific command via NETCONF, to cause a CPU Denial of Service to the device's control plane. This issue affects: Juniper Networks Junos OS * All versions prior to 20.4R3-S7; * 21.2 versions prior to 21.2R3-S5; * 21.3 versions prior to 21.3R3-S5; * 21.4 versions prior to 21.4R3-S4; * 22.1 versions prior to 22.1R3-S2; * 22.2 versions prior to 22.2R3; * 22.3 versions prior to 22.3R2-S1, 22.3R3; * 22.4 versions prior to 22.4R1-S2, 22.4R2. Juniper Networks Junos OS Evolved * All versions prior to 21.4R3-S4-EVO; * 22.1 versions prior to 22.1R3-S2-EVO; * 22.2 versions prior to 22.2R3-EVO; * 22.3 versions prior to 22.3R3-EVO; * 22.4 versions prior to 22.4R2-EVO. An indicator of compromise can be seen by first determining if the NETCONF client is logged in and fails to log out after a reasonable period of time and secondly reviewing the WCPU percentage for the mgd process by running the following command: mgd process example: user@device-re#> show system processes extensive | match "mgd|PID" | except last PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND 92476 root 100 0 500M 89024K CPU3 3 57.5H 89.60% mgd <<<<<<<<<<< review the high cpu percentage. Example to check for NETCONF activity: While there is no specific command that shows a specific session in use for NETCONF, you can review logs for UI_LOG_EVENT with "client-mode 'netconf'" For example: mgd[38121]: UI_LOGIN_EVENT: User 'root' login, class 'super-user' [38121], ssh-connection '10.1.1.1 201 55480 10.1.1.2 22', client-mode 'netconf'

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Junos OS Evolved · Juniper

95%

Affected range stops below 21.4, so it looks safe — our inference, not a vendor statement

Junos · Juniper Networks

95%

v < 20.4v < 20.4R3-S721.1 ≤ v < 21.1R121.2 ≤ v < 21.2R3-S521.3 ≤ v < 21.3R3-S521.4 ≤ v < 21.4R3-S422.1 ≤ v < 22.1R3-S222.2 ≤ v < 22.2R322.3 ≤ v < 22.3R2-S1, 22.3R322.4 ≤ v < 22.4R1-S2, 22.4R220.4 20.4 r1 20.4 r1-s1 20.4 r2 20.4 r2-s1 20.4 r2-s2 20.4 r3 20.4 r3-s1 20.4 r3-s2 20.4 r3-s3 20.4 r3-s4 20.4 r3-s5 20.4 r3-s6 21.1 21.2 21.2 r1 21.2 r1-s1 21.2 r1-s2 21.2 r2 21.2 r2-s1 21.2 r2-s2 21.2 r3 21.2 r3-s1 21.2 r3-s2 21.2 r3-s3 21.2 r3-s4 21.3 21.3 r1 21.3 r1-s1 21.3 r1-s2 21.3 r2 21.3 r2-s1 21.3 r2-s2 21.3 r3 21.3 r3-s1 21.3 r3-s2 21.3 r3-s3 21.3 r3-s4 21.4 21.4 r1 21.4 r1-s1 21.4 r1-s2 21.4 r2 21.4 r2-s1 21.4 r2-s2 21.4 r3 21.4 r3-s1 21.4 r3-s2 21.4 r3-s3 22.1 22.1 r1 22.1 r1-s1 22.1 r1-s2 22.1 r2 22.1 r2-s1 22.1 r2-s2 22.1 r3 22.1 r3-s1 22.2 22.2 r1 22.2 r1-s1 22.2 r1-s2 22.2 r2 22.2 r2-s1 22.2 r2-s2 22.3 22.3 r1 22.3 r1-s1 22.3 r1-s2 22.3 r2 22.4 22.4 r1 22.4 r1-s1

Affected range stops below 20.4, so it looks safe — our inference, not a vendor statement

Affected range stops below 20.4R3-S7, so it looks safe — our inference, not a vendor statement

Affected range stops below 21.1R1, so it looks safe — our inference, not a vendor statement

Affected range stops below 21.2R3-S5, so it looks safe — our inference, not a vendor statement

Affected range stops below 21.3R3-S5, so it looks safe — our inference, not a vendor statement

Affected range stops below 21.4R3-S4, so it looks safe — our inference, not a vendor statement

Affected range stops below 22.1R3-S2, so it looks safe — our inference, not a vendor statement

Affected range stops below 22.2R3, so it looks safe — our inference, not a vendor statement

Affected range stops below 22.3R2-S1, 22.3R3, so it looks safe — our inference, not a vendor statement

Affected range stops below 22.4R1-S2, 22.4R2, so it looks safe — our inference, not a vendor statement

Junos OS Evolved · Juniper Networks

60%

v < 21.4R3-S4-EVO22.1 ≤ v < 22.1R3-S2-EVO22.2 ≤ v < 22.2R3-EVO22.3 ≤ v < 22.3R3-EVO22.4 ≤ v < 22.4R2-EVO22.1 22.2 22.3 22.4

Affected range stops below 21.4R3-S4-EVO, so it looks safe — our inference, not a vendor statement

Affected range stops below 22.1R3-S2-EVO, so it looks safe — our inference, not a vendor statement

Affected range stops below 22.2R3-EVO, so it looks safe — our inference, not a vendor statement

Affected range stops below 22.3R3-EVO, so it looks safe — our inference, not a vendor statement

Affected range stops below 22.4R2-EVO, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

https://supportportal.juniper.net/JSA73147

References (1)

Vendor Advisory

Source: [email protected]

https://supportportal.juniper.net/JSA73147

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.5MEDIUMjuniper

Attack Vector: NETWORK
Complexity: LOW
Privileges: LOW
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: NONE
Integrity: NONE
Availability: HIGH

Vector?

Quick Info

StatusANALYZED

CWE

CWE-119

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card