Junos OS and Junos OS Evolved: Inconsistent information in the TE database can lead to an rpd crash
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 22.4R3-S1, 23.2R2, 22.4R3-S2-EVO, 23.2R2-EVO
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Juniper Networks Junos OS
From 22.4 · fixed in 22.4R3-S1; From 23.2 · fixed in 23.2R2
- Juniper Networks Junos OS Evolved
From 22.4-EVO · fixed in 22.4R3-S2-EVO; From 23.2-EVO · fixed in 23.2R2-EVO