Junos OS: SRX Series, MX Series with SPC3 and NFX350: When VPN tunnels parameters are not configured in specific way the iked process 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 21.2R3-S8, 21.4R3-S7, 22.1R3-S2, 22.2R3-S1
- 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 the IKE daemon (iked) of Juniper Networks Junos OS on SRX Series, MX Series with SPC3 and NFX350 allows allows an unauthenticated, network-based attacker sending specific mismatching parameters as part of the IPsec negotiation to trigger an iked crash leading to Denial of Service (DoS). This issue is applicable to all platforms that run iked. This issue affects Junos OS on SRX Series, MX Series with SPC3 and NFX350: • All versions before 21.2R3-S8, • from 21.4 before 21.4R3-S7, • from 22.1 before 22.1R3-S2, • from 22.2 before 22.2R3-S1, • from 22.3 before 22.3R2-S1, 22.3R3, • from 22.4 before 22.4R1-S2, 22.4R2, 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 21.2R3-S8; From 21.4 · fixed in 21.4R3-S7; From 22.1 · fixed in 22.1R3-S2; From 22.2 · fixed in 22.2R3-S1