Junos OS Evolved: Specific TCP traffic causes OFP core and restart of RE
- 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 21.2R3-S7-EVO, 21.3R3-S5-EVO, 21.4R3-S5-EVO, 22.1R3-S4-EVO, 22.2R3-S3-EVO, and 1 more
- 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 Handling of Syntactically Invalid Structure vulnerability in Object Flooding Protocol (OFP) service of Juniper Networks Junos OS Evolved allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). On all Junos OS Evolved platforms, when specific TCP packets are received on an open OFP port, the OFP crashes leading to a restart of Routine Engine (RE). Continuous receipt of these specific TCP packets will lead to a sustained Denial of Service (DoS) condition. This issue affects: Juniper Networks Junos OS Evolved • All versions earlier than 21.2R3-S7-EVO; • 21.3 versions earlier than 21.3R3-S5-EVO ; • 21.4 versions earlier than 21.4R3-S5-EVO; • 22.1 versions earlier than 22.1R3-S4-EVO; • 22.2 versions earlier than 22.2R3-S3-EVO ; • 22.3 versions earlier than 22.3R3-EVO; • 22.4 versions earlier than 22.4R2-EVO, 22.4R3-EVO.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Juniper Networks Junos OS Evolved
fixed in 21.2R3-S7-EVO; From 21.3 · fixed in 21.3R3-S5-EVO; From 21.4 · fixed in 21.4R3-S5-EVO; From 22.1 · fixed in 22.1R3-S4-EVO; From 22.2 · fixed in 22.2R3-S3-EVO; From 22.3 · fixed in 22.3R3-EVO