Junos OS and Junos OS Evolved: A high frequency of connecting and disconnecting NETCONF sessions causes management unavailability
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Juniper Networks | Junos OS | unaffected |
|
|||||||||||||||
| Juniper Networks | Junos OS Evolved | unaffected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
No data.
| Vendor | Product | Versions | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Juniper Networks | Junos Os |
|
||||||||||||||||||||||||
| Juniper Networks | Junos Os Evolved |
|
Vendor Solution
The following software releases have been updated to resolve this specific issue: Junos OS Evolved: 23.4R2-S5-EVO, 24.2R2-S1-EVO, 24.4R1-S3-EVO, 24.4R2-EVO, 25.2R1-EVO, and all subsequent releases; Junos OS: 23.4R2-S4, 24.2R2-S1, 24.4R1-S3, 24.4R2, 25.2R1, and all subsequent releases.
Vendor Workaround
Use access lists or firewall filters to limit access to the device only from trusted hosts and administrators. To further reduce the risk of exploitation you can set values as low as needed for your normal operations for: [ system services netconf ssh connection-limit <max_connections> ] [ system services netconf ssh rate-limit <connections_per_minute> ]
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.238% probability within 30 days)
| Link | Providers |
|---|---|
| https://kb.juniper.net/JSA106019 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Juniper
Juniper junos Juniper junos Os Evolved |
|
| CPEs | cpe:2.3:o:juniper:junos:23.4:-:*:*:*:*:*:* cpe:2.3:o:juniper:junos:23.4:r1-s1:*:*:*:*:*:* cpe:2.3:o:juniper:junos:23.4:r1-s2:*:*:*:*:*:* cpe:2.3:o:juniper:junos:23.4:r1:*:*:*:*:*:* cpe:2.3:o:juniper:junos:23.4:r2-s1:*:*:*:*:*:* cpe:2.3:o:juniper:junos:23.4:r2-s2:*:*:*:*:*:* cpe:2.3:o:juniper:junos:23.4:r2-s3:*:*:*:*:*:* cpe:2.3:o:juniper:junos:23.4:r2:*:*:*:*:*:* cpe:2.3:o:juniper:junos:24.2:-:*:*:*:*:*:* cpe:2.3:o:juniper:junos:24.2:r1-s1:*:*:*:*:*:* cpe:2.3:o:juniper:junos:24.2:r1-s2:*:*:*:*:*:* cpe:2.3:o:juniper:junos:24.2:r1:*:*:*:*:*:* cpe:2.3:o:juniper:junos:24.2:r2:*:*:*:*:*:* cpe:2.3:o:juniper:junos:24.4:-:*:*:*:*:*:* cpe:2.3:o:juniper:junos:24.4:r1-s2:*:*:*:*:*:* cpe:2.3:o:juniper:junos:24.4:r1:*:*:*:*:*:* cpe:2.3:o:juniper:junos:24.4:r2:*:*:*:*:*:* cpe:2.3:o:juniper:junos_os_evolved:23.4:-:*:*:*:*:*:* cpe:2.3:o:juniper:junos_os_evolved:23.4:r1-s1:*:*:*:*:*:* cpe:2.3:o:juniper:junos_os_evolved:23.4:r1-s2:*:*:*:*:*:* cpe:2.3:o:juniper:junos_os_evolved:23.4:r1:*:*:*:*:*:* cpe:2.3:o:juniper:junos_os_evolved:23.4:r2-s1:*:*:*:*:*:* cpe:2.3:o:juniper:junos_os_evolved:23.4:r2-s2:*:*:*:*:*:* cpe:2.3:o:juniper:junos_os_evolved:23.4:r2-s3:*:*:*:*:*:* cpe:2.3:o:juniper:junos_os_evolved:23.4:r2-s4:*:*:*:*:*:* cpe:2.3:o:juniper:junos_os_evolved:23.4:r2:*:*:*:*:*:* cpe:2.3:o:juniper:junos_os_evolved:24.2:-:*:*:*:*:*:* cpe:2.3:o:juniper:junos_os_evolved:24.2:r1-s2:*:*:*:*:*:* cpe:2.3:o:juniper:junos_os_evolved:24.2:r1:*:*:*:*:*:* cpe:2.3:o:juniper:junos_os_evolved:24.2:r2:*:*:*:*:*:* cpe:2.3:o:juniper:junos_os_evolved:24.4:-:*:*:*:*:*:* cpe:2.3:o:juniper:junos_os_evolved:24.4:r1-s2:*:*:*:*:*:* cpe:2.3:o:juniper:junos_os_evolved:24.4:r1:*:*:*:*:*:* cpe:2.3:o:juniper:junos_os_evolved:24.4:r2:*:*:*:*:*:* |
|
| Vendors & Products |
Juniper
Juniper junos Juniper junos Os Evolved |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Juniper Networks
Juniper Networks junos Os Juniper Networks junos Os Evolved |
|
| Vendors & Products |
Juniper Networks
Juniper Networks junos Os Juniper Networks junos Os Evolved |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | An Incorrect Synchronization vulnerability in the management daemon (mgd) of Juniper Networks Junos OS and Junos OS Evolved allows a network-based attacker with low privileges to cause a complete Denial-of-Service (DoS) of the management plane. When NETCONF sessions are quickly established and disconnected, a locking issue causes mgd processes to hang in an unusable state. When the maximum number of mgd processes has been reached, no new logins are possible. This leads to the inability to manage the device and requires a power-cycle to recover. This issue can be monitored by checking for mgd processes in lockf state in the output of 'show system processes extensive': user@host> show system processes extensive | match mgd <pid> root 20 0 501M 4640K lockf 1 0:01 0.00% mgd If the system still can be accessed (either via the CLI or as root, which might still be possible as last resort as this won't invoke mgd), mgd processes in this state can be killed with 'request system process terminate <PID>' from the CLI or with 'kill -9 <PID>' from the shell. This issue affects: Junos OS: * 23.4 versions before 23.4R2-S4, * 24.2 versions before 24.2R2-S1, * 24.4 versions before 24.4R1-S3, 24.4R2; This issue does not affect Junos OS versions before 23.4R1; Junos OS Evolved: * 23.4 versions before 23.4R2-S5-EVO, * 24.2 versions before 24.2R2-S1-EVO, * 24.4 versions before 24.4R1-S3-EVO, 24.4R2-EVO. This issue does not affect Junos OS Evolved versions before 23.4R1-EVO; | |
| Title | Junos OS and Junos OS Evolved: A high frequency of connecting and disconnecting NETCONF sessions causes management unavailability | |
| Weaknesses | CWE-821 | |
| References |
| |
| Metrics |
cvssV3_1
|