JunosOperating system · Juniper

CVE-2024-39541

MEDIUM · 6.5 CVSS v3.1 Published 2024-07-11

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

70/100

Remediation priority · Elevated

No privileges Zero-click

Official description

NVD · unedited

An Improper Handling of Exceptional Conditions vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, adjacent attacker to cause a Denial-of-Service (DoS). When conflicting information (IP or ISO addresses) about a node is added to the Traffic Engineering (TE) database and then a subsequent operation attempts to process these, rpd will crash and restart. This issue affects: Junos OS: * 22.4 versions before 22.4R3-S1, * 23.2 versions before 23.2R2, * 23.4 versions before 23.4R1-S1, 23.4R2, This issue does not affect Junos OS versions earlier than 22.4R1. Junos OS Evolved: * 22.4-EVO versions before 22.4R3-S2-EVO, * 23.2-EVO versions before 23.2R2-EVO, * 23.4-EVO versions before 23.4R1-S1-EVO, 23.4R2-EVO, This issue does not affect Junos OS Evolved versions earlier than before 22.4R1.

Technical summary

dbcve analysis · high confidence

A vulnerability in the Routing Protocol Daemon (rpd) of Juniper Junos OS and Junos OS Evolved allows an adjacent, unauthenticated attacker to cause a denial-of-service by crashing rpd. The issue occurs when conflicting IP or ISO addresses about a node are added to the Traffic Engineering (TE) database and subsequently processed, triggering an unhandled exceptional condition.

MitigationApply the vendor-supplied software updates (22.4R3-S1/22.4R3-S2-EVO and later, 23.2R2/23.2R2-EVO and later, or 23.4R1-S1/23.4R2/23.4R1-S1-EVO/23.4R2-EVO and later). As an interim control, restrict layer-2 adjacency and physical access to the routing infrastructure to prevent unauthorized attackers from injecting conflicting TE database entries.

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

Affected products & versions

NVD · CPE data

JunosOperating system

Affected:= 22.4= 23.2= 23.4

Junos Os EvolvedOperating system

Affected:= 22.4= 23.2= 23.4

CVSS breakdown

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?

dbcve checks

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

Identify the Junos OS version

Run 'show version' or 'show version detail' via CLI to retrieve the installed Junos OS version and build date

Affected if The version is 22.4 (any S variant), 23.2, or 23.4 (any S variant)
Confirm the product is Junos OS or Junos OS Evolved

Run 'show version' and check the 'Junos OS' or 'Junos OS Evolved' designation in the output

Affected if The device runs Junos OS or Junos OS Evolved in an affected version
Determine if Traffic Engineering (TE) database is configured

Run 'show configuration protocols mpls' and 'show configuration protocols isis' to check for traffic-engineering database or te-link configuration; also run 'show ted database' to list entries

Affected if TE database is actively configured or populated with entries
Verify adjacency exposure

Review interface configurations and network access controls to determine if layer-2 adjacency is exposed to untrusted network segments; check 'show interface' and physical port accessibility

Affected if The device has exposed layer-2 adjacency to untrusted or unauthorized network segments

The device is affected if it runs an affected Junos OS/Evolved version (22.4, 23.2, or 23.4) AND has Traffic Engineering database configured AND is accessible to adjacent attackers via exposed layer-2 interfaces.

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

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply the vendor-supplied software updates (22.4R3-S1/22.4R3-S2-EVO and later, 23.2R2/23.2R2-EVO and later, or 23.4R1-S1/23.4R2/23.4R1-S1-EVO/23.4R2-EVO and later). As an interim control, restrict layer-2 adjacency and physical access to the routing infrastructure to prevent unauthorized attackers from injecting conflicting TE database entries.

Recommended fix High confidence

Junos OS: 22.4R3-S1, 23.2R2, or 23.4R1-S1/23.4R2 and later; Junos OS Evolved: 22.4R3-S2-EVO, 23.2R2-EVO, or 23.4R1-S1-EVO/23.4R2-EVO and later

1. Identify the exact Junos OS or Junos OS Evolved version currently running using 'show version'
2. Based on the product type (Junos OS vs Junos OS Evolved), determine the appropriate upgrade path: for Junos OS upgrade to 22.4R3-S1 or later, 23.2R2 or later, or 23.4R1-S1/23.4R2 or later; for Junos OS Evolved upgrade to 22.4R3-S2-EVO or later, 23.2R2-EVO or later, or 23.4R1-S1-EVO/23.4R2-EVO or later
3. Schedule a maintenance window as rpd restart will cause temporary service interruption
4. Download the appropriate upgrade image from the Juniper Networks support portal
5. Upload the image to the device and initiate the upgrade using 'request system software add <package>'
6. After upgrade completes, verify the new version using 'show version' and confirm rpd is running using 'show routing-process'
7. Validate that the TE database functions normally with 'show ted database'

Caveat Standard Junos upgrade considerations apply - review release notes for any migration warnings; rpd restart will cause temporary routing interruption

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

Fix this in Junos Scoped from the published advisory

Consultation2.0 h
Implementation3.0 h
Testing4.0 h
Review / QA2.0 h

11.0 hours of engineering $1,900

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

supportportal.juniper.netVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2024-39541?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 6.5 Medium

Exploit likelihood EPSS, next 30 days 0.3%

Affects: Junos

Remediation

Need this fixed?

Fix this in Junos 11 hrs · Moderate

Typical engagement from $1,900

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2024-39541 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References