dbcve.org
JunosOperating system · Juniper

CVE-2024-39528

MEDIUM · 5.7 CVSS v3.1 Published 2024-07-11
Fix available
A fix is available. Upgrade to 21.2 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable

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
A Use After Free vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an authenticated, network-based attacker to cause a Denial of Service (DoS).On all Junos OS and Junos Evolved platforms, if a routing-instance deactivation is triggered, and at the same time a specific SNMP request is received, a segmentation fault occurs which causes rpd to crash and restart. This issue affects:    Junos OS: * All versions before 21.2R3-S8,  * 21.4 versions before 21.4R3-S5, * 22.2 versions before 22.2R3-S3, * 22.3 versions before 22.3R3-S2, * 22.4 versions before 22.4R3, * 23.2 versions before 23.2R2.   Junos OS Evolved: * All versions before 21.2R3-S8-EVO, * 21.4-EVO versions before 21.4R3-S5-EVO, * 22.2-EVO versions before 22.2R3-S3-EVO,  * 22.3-EVO versions before 22.3R3-S2-EVO, * 22.4-EVO versions before 22.4R3-EVO, * 23.2-EVO versions 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

Use After Free vulnerability in the Routing Protocol Daemon (rpd) on Juniper Junos OS and Junos OS Evolved. A race condition occurs when a routing-instance deactivation coincides with a specific SNMP request, causing a segmentation fault that crashes and restarts the rpd process, resulting in Denial of Service.

MitigationUpgrade Junos OS/Evolved to the specified patched versions (21.2R3-S8, 21.4R3-S5, 22.2R3-S3, 22.3R3-S2, 22.4R3, or 23.2R2 and later) to address the race condition in rpd.

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.2= 22.3= 22.4= 23.2
Junos Os EvolvedOperating system
Affected:< 21.2= 21.2= 21.4= 22.2= 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
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 the Junos OS version
    Run 'show version' or 'show version detail' on the device CLI to retrieve the installed Junos OS version
    Affected if The version matches < 21.2, = 21.2, = 21.4, = 22.2, = 22.3, = 22.4, or = 23.2 (for Junos) or matches the affected Evolved versions
  2. Confirm the product variant
    Run 'show version' and check if the output indicates 'Junos OS Evolved' versus standard 'Junos OS'
    Affected if The device runs either Junos OS or Junos OS Evolved with an affected version
  3. Verify SNMP is configured
    Run 'show configuration snmp' to check if SNMP is enabled on the device
    Affected if SNMP is configured and enabled - this is required for the attack vector
  4. Check for rpd crash logs
    Run 'show log messages' or 'show system core-dumps' and search for recent rpd crashes or restarts, particularly with segmentation fault indicators
    Affected if Recent rpd crashes or restarts are present in logs, especially if accompanied by SNMP query timing
  5. Identify configured routing instances
    Run 'show configuration routing-instances' to list all routing instances configured on the device
    Affected if One or more routing instances are configured - these are subject to the deactivation race condition

The device is likely affected if it runs a vulnerable Junos version AND has SNMP enabled with routing instances configured, particularly if rpd crashes are observed in logs.

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

Upgrade Junos OS/Evolved to the specified patched versions (21.2R3-S8, 21.4R3-S5, 22.2R3-S3, 22.3R3-S2, 22.4R3, or 23.2R2 and later) to address the race condition in rpd.

Recommended fix High confidence

Upgrade to the fixed version for your release train: Junos OS 21.2R3-S8/21.4R3-S5/22.2R3-S3/22.3R3-S2/22.4R3/23.2R2 or later; Junos OS Evolved 21.2R3-S8-EVO/21.4R3-S5-EVO/22.2R3-S3-EVO/22.3R3-S2-EVO/22.4R3-EVO/23.2R2-EVO or later

  1. 1. Identify the current Junos OS or Junos OS Evolved version installed on the device using 'show version'
  2. 2. Determine which release train your current version belongs to (21.2, 21.4, 22.2, 22.3, 22.4, or 23.2)
  3. 3. For Junos OS: upgrade to the appropriate fixed version based on your current release train: 21.2R3-S8, 21.4R3-S5, 22.2R3-S3, 22.3R3-S2, 22.4R3, or 23.2R2 or later
  4. 4. For Junos OS Evolved: upgrade to the appropriate fixed version based on your current release train: 21.2R3-S8-EVO, 21.4R3-S5-EVO, 22.2R3-S3-EVO, 22.3R3-S2-EVO, 22.4R3-EVO, or 23.2R2-EVO or later
  5. 5. Download the upgrade package from the Juniper Networks support portal
  6. 6. Upload the upgrade package to the device using 'file copy' or USB
  7. 7. Install the upgrade using 'request system software add <package>' with appropriate options (e.g., 'reboot' flag)
  8. 8. After reboot, verify the new version is running with 'show version'
Caveat Standard Junos upgrade risks apply - verify hardware compatibility and test in lab before production deployment; some feature behavior may change across major release trains

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

Fix this in Junos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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