Junos OS: SRX4600 and SRX5000 Series: Sequence of specific PIM packets causes a flowd 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 21.4R3-S9, 22.2R3-S5, 22.3R3-S4, 22.4R3-S4, 23.2R2-S2, 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: no
- Technical impact: partial
Summary
An Improper Check for Unusual or Exceptional Conditions vulnerability in the flow processing daemon (flowd) of Juniper Networks Junos OS on SRX4600 and SRX5000 Series allows an unauthenticated and logically adjacent attacker to cause a Denial-of-Service (DoS). If in a multicast scenario a sequence of specific PIM packets is received, this will cause a flowd crash and restart, which leads to momentary service interruption. This issue affects Junos OS on SRX 4600 and SRX 5000 Series: • All versions before 21.4R3-S9, • 22.2 versions before 22.2R3-S5, • 22.3 versions before 22.3R3-S4, • 22.4 versions before 22.4R3-S4, • 23.2 versions before 23.2R2-S2, • 23.4 versions before 23.4R2, • 24.2 versions before 24.2R1-S1, 24.2R2.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Juniper Networks Junos OS
fixed in 21.4R3-S9; From 22.2 · fixed in 22.2R3-S5; From 22.3 · fixed in 22.3R3-S4; From 22.4 · fixed in 22.4R3-S4; From 23.2 · fixed in 23.2R2-S2; From 23.4 · fixed in 23.4R2