Junos OS: MX with SPC3, SRX Series: A specifically malformed TCP packet 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 23.4R2-S7, 24.2R2-S4, 24.4R2-S3, 25.2R2
- 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 Validation of Specified Quantity in Input vulnerability in the TCP proxy plugin of Juniper Networks Junos OS on MX Series with SPC3, and SRX Series allows an unauthenticated, network-based attacker to cause a complete Denial of Service (DoS). When TCP proxy is engaged in a flow session, to support ALGs, Advanced Anti-Malware, ICAP or UTM, a TCP packet with specifically malformed TCP header will cause flow processing daemon (flowd) to crash and restart. This causes a complete service outage until the system has automatically recovered. This issue affects Junos OS on MX with SPC3, and SRX Series: • 23.4 versions before 23.4R2-S7, • 24.2 versions before 24.2R2-S4, • 24.4 versions before 24.4R2-S3, • 25.2 versions before 25.2R2. This issue does not affect releases before 23.4R1.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Juniper Networks Junos OS
From 23.4 · fixed in 23.4R2-S7; From 24.2 · fixed in 24.2R2-S4; From 24.4 · fixed in 24.4R2-S3; From 25.2 · fixed in 25.2R2