dbcve.org
JunosOperating system · Juniper

CVE-2024-39543

MEDIUM · 6.5 CVSS v3.1 Published 2024-07-11
Fix available
A fix is available. Upgrade to 21.2 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
A Buffer Copy without Checking Size of Input vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Juniper Networks Junos OS Evolved allows an unauthenticated, adjacent attacker to send specific RPKI-RTR packets resulting in a crash, creating a Denial of Service (DoS) condition. Continued receipt and processing of this packet will create a sustained Denial of Service (DoS) condition. This issue affects  Junos OS:  * All versions before 21.2R3-S8,  * from 21.4 before 21.4R3-S8, * from 22.2 before 22.2R3-S4,  * from 22.3 before 22.3R3-S3,  * from 22.4 before 22.4R3-S2,  * from 23.2 before 23.2R2-S1,  * from 23.4 before 23.4R2. Junos OS Evolved: * All versions before 21.2R3-S8-EVO, * from 21.4 before 21.4R3-S8-EVO, * from 22.2 before 22.2R3-S4-EVO,  * from 22.3 before 22.3R3-S3-EVO, * from 22.4 before 22.4R3-S2-EVO,  * from 23.2 before 23.2R2-S1-EVO, * from 23.4 before 23.4R2-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

A buffer overflow vulnerability exists in the routing protocol daemon (rpd) when processing RPKI-RTR packets. An unauthenticated adjacent attacker can send specially crafted RPKI-RTR packets that cause rpd to crash due to unchecked buffer copy operations, creating a sustained DoS condition.

MitigationApply the vendor-provided patches/updates to upgrade to the fixed versions (21.2R3-S8, 21.4R3-S8, 22.2R3-S4, 22.3R3-S3, 22.4R3-S2, 23.2R2-S1, 23.4R2 or later). As an interim mitigation, restrict adjacent network access to RPKI-RTR ports (TCP 323 or 8282) via firewall rules.

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= 23.4
Junos Os EvolvedOperating system
Affected:< 21.2= 21.2= 21.4= 22.2= 22.3= 22.4= 23.2= 23.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
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. Identify the installed Junos version
    Run the command 'show version' or 'show version detail' on the device CLI to obtain the exact software version.
    Affected if The version matches one of the affected ranges: any version < 21.2, or = 21.2, = 21.4, = 22.2, = 22.3, = 22.4, = 23.2, = 23.4.
  2. Confirm the product is Junos or Junos Evolved
    Review the 'show version' output to identify whether the device runs Junos (classic) or Junos OS Evolved, as both product lines are affected.
    Affected if The device runs either Juniper Junos or Juniper Junos OS Evolved in any of the affected versions listed.
  3. Determine if RPKI-RTR protocol is enabled
    Execute 'show configuration routing-options rpki' or 'show rpki status' to check whether RPKI-RTR is configured on the device.
    Affected if RPKI-RTR is actively configured or enabled; the vulnerability only applies when this feature is in use.
  4. Check for listening RPKI-RTR ports
    Use 'show system services rpki' or check open ports (TCP 323 or 8282) to see if the RPKI-RTR service is listening for connections.
    Affected if The RPKI-RTR service is listening on TCP ports 323 or 8282, indicating the attack surface is exposed.
  5. Inspect active RPKI-RTR sessions
    Run 'show rpki connections' or similar command to view established or pending RPKI-RTR sessions with validators.
    Affected if There are active RPKI-RTR sessions, confirming the protocol is in use and potentially reachable.

A device is affected if it runs a vulnerable Junos/Junos Evolved version AND has RPKI-RTR protocol enabled and listening, exposing the rpd to crafted RPKI-RTR packets from adjacent attackers.

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 vendor-provided patches/updates to upgrade to the fixed versions (21.2R3-S8, 21.4R3-S8, 22.2R3-S4, 22.3R3-S3, 22.4R3-S2, 23.2R2-S1, 23.4R2 or later). As an interim mitigation, restrict adjacent network access to RPKI-RTR ports (TCP 323 or 8282) via firewall rules.

Recommended fix High confidence

For Junos OS: upgrade to 21.2R3-S8 / 21.4R3-S8 / 22.2R3-S4 / 22.3R3-S3 / 22.4R3-S2 / 23.2R2-S1 / 23.4R2 or later. For Junos OS Evolved: upgrade to 21.2R3-S8-EVO / 21.4R3-S8-EVO / 22.2R3-S4-EVO / 22.3R3-S3-EVO / 22.4R3-S2-EVO / 23.2R2-S1-EVO / 23.4R2-EVO or later.

  1. 1. Identify the current Junos OS or Junos OS Evolved version by running 'show version' command.
  2. 2. Determine the appropriate upgrade path based on the current branch (21.2, 21.4, 22.2, 22.3, 22.4, 23.2, or 23.4).
  3. 3. For Junos OS: upgrade to the minimum fixed version for your branch (21.2R3-S8, 21.4R3-S8, 22.2R3-S4, 22.3R3-S3, 22.4R3-S2, 23.2R2-S1, or 23.4R2 or higher).
  4. 4. For Junos OS Evolved: upgrade to the minimum fixed version for your branch (21.2R3-S8-EVO, 21.4R3-S8-EVO, 22.2R3-S4-EVO, 22.3R3-S3-EVO, 22.4R3-S2-EVO, 23.2R2-S1-EVO, or 23.4R2-EVO or higher).
  5. 5. Schedule a maintenance window as upgrades require system reboot.
  6. 6. Back up the current configuration using 'request system configuration rescue save'.
  7. 7. Download the appropriate upgrade package from the Juniper Networks support portal.
  8. 8. Perform the upgrade using 'request system software add <package-name>' for Junos OS or follow the specific upgrade procedure for Junos OS Evolved.
Caveat Standard Junos upgrade considerations apply - ensure compatibility with existing configuration and review release notes for any behavioral changes. The RPKI-RTR protocol must be re-enabled after upgrade if it was disabled as a mitigation.

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

Fix this in Junos Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
32.0 hours of engineering $5,520
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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