dbcve.org
JunosOperating system · Juniper

CVE-2024-39545

HIGH · 7.5 CVSS v3.1 Published 2024-07-11
Fix available
A fix is available. Upgrade to 21.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A vulnerability in the IKE daemon (iked) of Juniper Junos OS on SRX Series, MX Series with SPC3, and NFX350 allows an unauthenticated network attacker to crash the iked process by sending IPsec negotiation requests with specific mismatching parameters. The daemon fails to properly handle these unusual conditions, resulting in a denial of service.

MitigationApply the appropriate Junos OS patch based on the version matrix (21.2R3-S8, 21.4R3-S7, 22.1R3-S2, 22.2R3-S1, 22.3R2-S1/22.3R3, 22.4R1-S2/22.4R2/22.4R3 or later). As an interim measure, restrict IKE traffic to trusted sources using firewall policies.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JunosOperating system
Affected:< 21.2= 21.2= 21.4= 22.1= 22.2= 22.3= 22.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Junos OS version
    Run 'show version' on the device and locate the Junos OS version number in the output
    Affected if The version is 21.2, 21.4, 22.1, 22.2, 22.3, or 22.4, or any version earlier than 21.2 (for example 20.4, 20.3, etc.)
  2. Confirm iked process is running
    Run 'show system processes process-name iked' or check process status via 'request system process daemon iked status'
    Affected if The iked daemon is actively running on the device
  3. Verify IKE/IPsec is configured
    Run 'show configuration security ike' to display IKE configuration, or 'show security ike security-associations' to show active IKE SAs
    Affected if IKE is configured and active, meaning the device accepts IPsec negotiations on any interface
  4. Check device model is affected platform
    Run 'show chassis hardware' or 'show version' to identify the device model; confirm it is SRX Series, MX Series with SPC3, or NFX350
    Affected if The device is an SRX Series, MX Series with SPC3, or NFX350

The device is affected if it is a vulnerable SRX, MX (with SPC3), or NFX350 model running Junos OS version 21.2 through 22.4 or any version before 21.2, with IKE/IPsec functionality enabled and the iked process running.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 21.2 or later
Fixed in 21.2
Interim mitigation

Apply the appropriate Junos OS patch based on the version matrix (21.2R3-S8, 21.4R3-S7, 22.1R3-S2, 22.2R3-S1, 22.3R2-S1/22.3R3, 22.4R1-S2/22.4R2/22.4R3 or later). As an interim measure, restrict IKE traffic to trusted sources using firewall policies.

Recommended fix High confidence

Upgrade to 21.2R3-S8 / 21.4R3-S7 / 22.1R3-S2 / 22.2R3-S1 / 22.3R2-S1 or 22.3R3 / 22.4R1-S2, 22.4R2, or 22.4R3 (depending on your current branch)

  1. 1. Identify the current Junos OS version running on affected devices (SRX Series, MX Series with SPC3, NFX350) using 'show version' command
  2. 2. Based on the current version, plan upgrade to the appropriate fixed release:
  3. - If on 21.2.x: upgrade to 21.2R3-S8 or later
  4. - If on 21.4.x: upgrade to 21.4R3-S7 or later
  5. - If on 22.1.x: upgrade to 22.1R3-S2 or later
  6. - If on 22.2.x: upgrade to 22.2R3-S1 or later
  7. - If on 22.3.x: upgrade to 22.3R2-S1 or 22.3R3 or later
  8. - If on 22.4.x: upgrade to 22.4R1-S2, 22.4R2, or 22.4R3 or later
Caveat Standard Junos upgrade precautions apply - test in lab first, schedule maintenance window, ensure configuration backup exists

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-39545 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-39545 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data