Junos OS: SRX 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.2R3-S9, 21.4R3-S11, 22.2R3-S7, 22.4R3-S6, 23.2R2-S4, and 2 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 Check for Unusual or Exceptional Conditions vulnerability in the flow processing daemon (flowd) of Juniper Networks Junos OS on SRX1600, SRX2300, SRX 4000 Series, and SRX5000 Series with SPC3 allows an unauthenticated, network-based attacker to cause a Denial-of-Service (DoS). If a sequence of specific PIM packets is received, this will cause a flowd crash and restart. This issue affects Junos OS: • all versions before 21.2R3-S9, • 21.4 versions before 21.4R3-S11, • 22.2 versions before 22.2R3-S7, • 22.4 versions before 22.4R3-S6, • 23.2 versions before 23.2R2-S4, • 23.4 versions before 23.4R2-S4, • 24.2 versions before 24.2R2. This is a similar, but different vulnerability than the issue reported as CVE-2024-47503, published in JSA88133.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Juniper Networks Junos OS
fixed in 21.2R3-S9; From 21.4 · fixed in 21.4R3-S11; From 22.2 · fixed in 22.2R3-S7; From 22.4 · fixed in 22.4R3-S6; From 23.2 · fixed in 23.2R2-S4; From 23.4 · fixed in 23.4R2-S4; From 24.2 · fixed in 24.2R2