dbcve.org
JunosOperating system · Juniper

CVE-2024-39514

MEDIUM · 6.5 CVSS v3.1 Published 2024-07-10
Fix available
A fix is available. Upgrade to 20.4 or later.
See remediation →
70/100
Remediation priority · Elevated
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 or Handling of Exceptional Conditions vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos and Junos OS Evolved allows an unauthenticated, adjacent attacker to cause a Denial of Service (DoS). An attacker can send specific traffic to the device, which causes the rpd to crash and restart. Continued receipt of this traffic will result in a sustained DoS condition. This issue only affects devices with an EVPN-VPWS instance with IGMP-snooping enabled. This issue affects Junos OS: * All versions before 20.4R3-S10,  * from 21.4 before 21.4R3-S6,  * from 22.1 before 22.1R3-S5,  * from 22.2 before 22.2R3-S3,  * from 22.3 before 22.3R3-S2,  * from 22.4 before 22.4R3,  * from 23.2 before 23.2R2; Junos OS Evolved: * All versions before 20.4R3-S10-EVO,  * from 21.4-EVO before 21.4R3-S6-EVO,  * from 22.1-EVO before 22.1R3-S5-EVO,  * from 22.2-EVO before 22.2R3-S3-EVO,  * from 22.3-EVO before 22.3R3-S2-EVO,  * from 22.4-EVO before 22.4R3-EVO,  * from 23.2-EVO before 23.2R2-EVO.

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

Improper check/handling of exceptional conditions in the Routing Protocol Daemon (rpd) allows an unauthenticated adjacent attacker to crash and restart rpd by sending specific traffic to devices with EVPN-VPWS instances that have IGMP-snooping enabled, causing sustained DoS.

MitigationApply the appropriate Junos OS or Junos OS Evolved software update from the advisory. As a workaround, consider disabling IGMP-snooping on EVPN-VPWS instances if immediate patching is not feasible.

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:< 20.4= 20.4= 21.4= 22.1= 22.2= 22.3= 22.4= 23.2
Junos Os EvolvedOperating system
Affected:< 20.4= 20.4= 21.4= 22.1= 22.2= 22.3= 22.4= 23.2

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/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. Check Junos version
    Run 'show version' or 'show version detail' to display the installed Junos OS or Junos OS Evolved version
    Affected if The displayed version is < 20.4, or equals 20.4, 21.4, 22.1, 22.2, 22.3, 22.4, or 23.2
  2. Verify EVPN-VPWS instance configuration
    Run 'show configuration protocols evpn vpws' or 'show configuration instance <instance-name> protocols evpn-vpws' to list configured EVPN-VPWS instances
    Affected if Any EVPN-VPWS instances are configured on the device
  3. Check IGMP-snooping status on EVPN-VPWS
    Run 'show igmp snooping interface' or 'show configuration protocols igmp-snooping' to determine if IGMP-snooping is enabled; for specific instances, check 'show configuration protocols evpn vpws <instance-name> igmp-snooping'
    Affected if IGMP-snooping is enabled on any EVPN-VPWS instance (the vulnerability only affects devices with both EVPN-VPWS and IGMP-snooping enabled)
  4. Confirm rpd process is running
    Run 'show system processes routing' or 'show system processes rpd' to verify the routing daemon is active
    Affected if The rpd process is running (the crash affects this process when the vulnerable condition is triggered)

You are affected if your Junos version matches the listed vulnerable versions AND you have EVPN-VPWS instances with IGMP-snooping enabled.

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 20.4 or later
Fixed in 20.4
Interim mitigation

Apply the appropriate Junos OS or Junos OS Evolved software update from the advisory. As a workaround, consider disabling IGMP-snooping on EVPN-VPWS instances if immediate patching is not feasible.

Recommended fix High confidence

Upgrade to 23.2R2 or later (or the latest 22.4R3 release) for Junos OS; or 23.2R2-EVO or later for Junos OS Evolved

  1. 1. Identify the current Junos or Junos OS Evolved version using 'show version' command
  2. 2. Determine the current branch (e.g., 20.4, 21.4, 22.1, 22.2, 22.3, 22.4, 23.2)
  3. 3. For Junos OS: upgrade to the appropriate fixed release: 20.4R3-S10, 21.4R3-S6, 22.1R3-S5, 22.2R3-S3, 22.3R3-S2, 22.4R3, or 23.2R2 (or later)
  4. 4. For Junos OS Evolved: upgrade to 20.4R3-S10-EVO, 21.4R3-S6-EVO, 22.1R3-S5-EVO, 22.2R3-S3-EVO, 22.3R3-S2-EVO, 22.4R3-EVO, or 23.2R2-EVO (or later)
  5. 5. Upload the Junos upgrade package via FTP/SCP to the device
  6. 6. Execute 'request system software add <package>' to install the upgrade
  7. 7. Reboot the device using 'request system reboot' to apply changes
  8. 8. After reboot, verify the fix using 'show version' to confirm the new version is running
Caveat Standard Junos upgrade considerations apply - review release notes for compatibility with other installed packages and line cards; test in lab before production deployment

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

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-39514 — 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-39514 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