Junos OS: SRX Series: When "tcp-encap" is configured and specific packets are received flowd will 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 20.4R3-S8, 21.2R3-S6, 21.3R3-S5, 21.4R3-S5, 22.1R3-S3, 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
A Double Free vulnerability in the flow processing daemon (flowd) of Juniper Networks Junos OS on SRX Series allows a network-based, unauthenticated attacker to cause a Denial of Service (DoS). In a remote access VPN scenario, if a "tcp-encap-profile" is configured and a sequence of specific packets is received, a flowd crash and restart will be observed. This issue affects Juniper Networks Junos OS on SRX Series: • All versions earlier than 20.4R3-S8; • 21.2 versions earlier than 21.2R3-S6; • 21.3 versions earlier than 21.3R3-S5; • 21.4 versions earlier than 21.4R3-S5; • 22.1 versions earlier than 22.1R3-S3; • 22.2 versions earlier than 22.2R3-S3; • 22.3 versions earlier than 22.3R3-S1; • 22.4 versions earlier than 22.4R2-S2, 22.4R3.
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-S8; From 21.2 · fixed in 21.2R3-S6; From 21.3 · fixed in 21.3R3-S5; From 21.4 · fixed in 21.4R3-S5; From 22.1 · fixed in 22.1R3-S3; From 22.2 · fixed in 22.2R3-S3; From 22.3 · fixed in 22.3R3-S1