Junos OS: SRX4600, SRX5000 Series: TCP packets with SYN/FIN or SYN/RST are transferred after enabling no-syn-check with Express Path
- 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-S8, 21.4R3-S7, 22.1R3-S6, 22.2R3-S4, 22.3R3-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
An Improper Check for Unusual or Exceptional Conditions vulnerability in the flow daemon (flowd) of Juniper Networks Junos OS on SRX4600 and SRX5000 Series allows an attacker to send TCP packets with SYN/FIN or SYN/RST flags, bypassing the expected blocking of these packets. A TCP packet with SYN/FIN or SYN/RST should be dropped in flowd. However, when no-syn-check and Express Path are enabled, these TCP packets are unexpectedly transferred to the downstream network. This issue affects Junos OS on SRX4600 and SRX5000 Series: • All versions before 21.2R3-S8, • from 21.4 before 21.4R3-S7, • from 22.1 before 22.1R3-S6, • from 22.2 before 22.2R3-S4, • from 22.3 before 22.3R3-S3, • from 22.4 before 22.4R3-S2, • from 23.2 before 23.2R2, • from 23.4 before 23.4R1-S1, 23.4R2.
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-S8; From 21.4 · fixed in 21.4R3-S7; From 22.1 · fixed in 22.1R3-S6; From 22.2 · fixed in 22.2R3-S4; From 22.3 · fixed in 22.3R3-S3; From 22.4 · fixed in 22.4R3-S2; From 23.2 · fixed in 23.2R2