An Improper Handling of Exceptional Conditions vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, adjacent attacker to cause a Denial-of-Service (DoS). When conflicting information (IP or ISO addresses) about a node is added to the Traffic Engineering (TE) database and then a subsequent operation attempts to process these, rpd will crash and restart. This issue affects: Junos OS: * 22.4 versions before 22.4R3-S1, * 23.2 versions before 23.2R2, * 23.4 versions before 23.4R1-S1, 23.4R2, This issue does not affect Junos OS versions earlier than 22.4R1. Junos OS Evolved: * 22.4-EVO versions before 22.4R3-S2-EVO, * 23.2-EVO versions before 23.2R2-EVO, * 23.4-EVO versions before 23.4R1-S1-EVO, 23.4R2-EVO, This issue does not affect Junos OS Evolved versions earlier than before 22.4R1.
This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 6.5, indicating it requires adjacent network access with relatively low complexity without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts and availability (service disruption) for affected systems. Impacting 2 products from juniper, from juniper organizations running these solutions should prioritize assessment and patching.
Reported in 2024, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.
2024-07-11T17:15:13.127
2026-01-23T19:24:10.423
Analyzed
CVSSv3.1: 6.5 (MEDIUM)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Operating System | juniper | junos | 22.4 | Yes |
| Operating System | juniper | junos | 22.4 | Yes |
| Operating System | juniper | junos | 22.4 | Yes |
| Operating System | juniper | junos | 22.4 | Yes |
| Operating System | juniper | junos | 22.4 | Yes |
| Operating System | juniper | junos | 22.4 | Yes |
| Operating System | juniper | junos | 22.4 | Yes |
| Operating System | juniper | junos | 22.4 | Yes |
| Operating System | juniper | junos | 23.2 | Yes |
| Operating System | juniper | junos | 23.2 | Yes |
| Operating System | juniper | junos | 23.2 | Yes |
| Operating System | juniper | junos | 23.2 | Yes |
| Operating System | juniper | junos | 23.4 | Yes |
| Operating System | juniper | junos | 23.4 | Yes |
| Operating System | juniper | junos | 23.4 | Yes |
| Operating System | juniper | junos_os_evolved | 22.4 | Yes |
| Operating System | juniper | junos_os_evolved | 22.4 | Yes |
| Operating System | juniper | junos_os_evolved | 22.4 | Yes |
| Operating System | juniper | junos_os_evolved | 22.4 | Yes |
| Operating System | juniper | junos_os_evolved | 22.4 | Yes |
| Operating System | juniper | junos_os_evolved | 22.4 | Yes |
| Operating System | juniper | junos_os_evolved | 22.4 | Yes |
| Operating System | juniper | junos_os_evolved | 22.4 | Yes |
| Operating System | juniper | junos_os_evolved | 22.4 | Yes |
| Operating System | juniper | junos_os_evolved | 23.2 | Yes |
| Operating System | juniper | junos_os_evolved | 23.2 | Yes |
| Operating System | juniper | junos_os_evolved | 23.2 | Yes |
| Operating System | juniper | junos_os_evolved | 23.2 | Yes |
| Operating System | juniper | junos_os_evolved | 23.4 | Yes |
| Operating System | juniper | junos_os_evolved | 23.4 | Yes |
| Operating System | juniper | junos_os_evolved | 23.4 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For juniper's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.