Junos OS: MX Series: In a PTP scenario a prolonged routing protocol churn can trigger an FPC reboot
- 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 20.4R3-S4, 21.2R3-S2, 21.3R3-S5, 21.4R3, 22.1R3
- 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: yes
- Technical impact: partial
Summary
An Improper Check for Unusual or Exceptional Conditions vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on MX Series allows a network-based, unauthenticated attacker to cause a Denial of Service (DoS). On Junos MX Series platforms with Precision Time Protocol (PTP) configured, a prolonged routing protocol churn can lead to an FPC crash and restart. This issue affects Juniper Networks Junos OS on MX Series: • All versions prior to 20.4R3-S4; • 21.1 version 21.1R1 and later versions; • 21.2 versions prior to 21.2R3-S2; • 21.3 versions prior to 21.3R3-S5; • 21.4 versions prior to 21.4R3; • 22.1 versions prior to 22.1R3; • 22.2 versions prior to 22.2R1-S1, 22.2R2.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Juniper Networks Junos OS
fixed in 20.4R3-S4; From 21.1R1; From 21.2 · fixed in 21.2R3-S2; From 21.3 · fixed in 21.3R3-S5; From 21.4 · fixed in 21.4R3; From 22.1 · fixed in 22.1R3