Junos OS (SRX firewalls)
CVE-2024-39545: SRX Series, MX Series with SPC3 and NFX350: When VPN tunnels parameters are not configured in specific way the iked process will crash
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).
Published
Automatic summary from the vendor's CVE record. We haven't written a full analysis of this vulnerability yet.
Affected and fixed versions
| Product / branch | Fixed in |
|---|---|
| Junos OS (SRX Series, MX Series with SPC3, NFX350) 0 | 21.2R3-S8 or later |
| Junos OS (SRX Series, MX Series with SPC3, NFX350) 21.4 | 21.4R3-S7 or later |
| Junos OS (SRX Series, MX Series with SPC3, NFX350) 22.1 | 22.1R3-S2 or later |
| Junos OS (SRX Series, MX Series with SPC3, NFX350) 22.2 | 22.2R3-S1 or later |
| Junos OS (SRX Series, MX Series with SPC3, NFX350) 22.3 | 22.3R2-S1, 22.3R3 or later |
| Junos OS (SRX Series, MX Series with SPC3, NFX350) 22.4 | 22.4R1-S2, 22.4R2, 22.4R3 or later |
Always confirm against the vendor advisory, which lists every fixed hotfix.
What it is
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.
Am I affected?
To be exposed to this issue IPsec VPN needs to be configured with a minimal ike configuration:
[ security ike gateway ike-policy ]
[ security ipsec vpn ike gateway ]
Also, the system needs to run iked (vs. kmd which is not affected), which can be verified with:
show system processes extensive | match "KMD|IKED"
Workarounds
There are no known workarounds for this issue.
Exploitation
Juniper SIRT is not aware of any malicious exploitation of this vulnerability.
Sources
KEV status, EPSS score and vendor data refreshed automatically, last on 13 Oct 2026.