dbcve.org
Junos Os EvolvedOperating system · Juniper

CVE-2024-21590

MEDIUM · 6.5 CVSS v3.1 Published 2024-04-12
Fix available
A fix is available. Upgrade to after 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
An Improper Input Validation vulnerability in Juniper Tunnel Driver (jtd) and ICMP module of Juniper Networks Junos OS Evolved allows an unauthenticated attacker within the MPLS administrative domain to send specifically crafted packets to the Routing Engine (RE) to cause a Denial of Service (DoS).  When specifically crafted transit MPLS IPv4 packets are received by the Packet Forwarding Engine (PFE), these packets are internally forwarded to the RE. Continued receipt of these packets may create a sustained Denial of Service (DoS) condition. This issue affects Juniper Networks Junos OS: * All versions before 21.2R3-S8-EVO; * from 21.4-EVO before 21.4R3-S6-EVO; * from 22.2-EVO before 22.2R3-S4-EVO; * from 22.3-EVO before 22.3R3-S3-EVO; * from 22.4-EVO before 22.4R3-EVO; * from 23.2-EVO before 23.2R2-EVO. * from 23.4-EVO before 23.4R1-S1-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 input validation in Juniper Tunnel Driver (jtd) and ICMP module of Junos OS Evolved allows an unauthenticated attacker within the MPLS administrative domain to send crafted MPLS IPv4 packets. These packets are forwarded from the PFE to the RE, causing a sustained DoS condition on the Routing Engine.

MitigationApply the vendor-supplied patches for the specific version branches. As an interim measure, restrict MPLS administrative domain access to trusted sources and filter suspicious MPLS packets at network boundaries.

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
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. Confirm Junos OS Evolved is running
    Run 'show version' or 'cat /etc/hostname' to identify the OS. This vulnerability affects ONLY Junos OS Evolved, not standard Junos OS.
    Affected if The device runs standard Junos OS instead of Junos OS Evolved - in that case, this specific CVE does not apply.
  2. Check installed version against affected list
    Run 'show version' and look at the 'junos-evolved' version string. Compare it to the affected versions: <=21.2, 21.2, 21.4, 22.2, 22.3, 22.4, 23.2, 23.4.
    Affected if The installed Junos OS Evolved version matches or falls within the affected version ranges listed.
  3. Verify MPLS is enabled
    Run 'show configuration protocols mpls' or 'show configuration protocols label-switched-path' to check if MPLS protocols are configured.
    Affected if MPLS is actively configured on the device - the vulnerability requires MPLS to be in use.
  4. Check MPLS interface exposure
    Run 'show mpls interface' to list interfaces with MPLS enabled. Assess whether these interfaces are accessible from untrusted MPLS domains.
    Affected if MPLS interfaces are exposed to untrusted or external MPLS administrative domains.
  5. Inspect MPLS packet forwarding behavior
    Monitor logs and packet counts for MPLS IPv4 traffic: 'show mpls statistics' and check system logs for ICMP or jtd module anomalies.
    Affected if Unusual or malformed MPLS IPv4 packets are being forwarded from PFE to RE, or ICMP module errors appear in system logs.

A device is affected if it runs Junos OS Evolved (not standard Junos OS), is on an affected version (21.2 through 23.4), and has MPLS enabled with interfaces exposed to the MPLS administrative domain where the attacker resides.

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 a release after 21.2
Interim mitigation

Apply the vendor-supplied patches for the specific version branches. As an interim measure, restrict MPLS administrative domain access to trusted sources and filter suspicious MPLS packets at network boundaries.

Recommended fix High confidence

Upgrade to 21.2R3-S8-EVO (or later from your current branch: 21.4R3-S6-EVO, 22.2R3-S4-EVO, 22.3R3-S3-EVO, 22.4R3-EVO, 23.2R2-EVO, or 23.4R1-S1-EVO depending on your release line)

  1. 1. Identify the current Junos OS Evolved version using 'show version' command
  2. 2. Determine the appropriate upgrade path based on current version (see upgrade_path field)
  3. 3. Schedule a maintenance window as this upgrade requires system downtime
  4. 4. Download the appropriate fixed EVO image from Juniper Networks support portal
  5. 5. Upload the new image to the device using 'request system software add' command
  6. 6. Reboot the device using 'request system reboot' command
  7. 7. After reboot, verify the new version is running with 'show version'
  8. 8. Confirm the vulnerability is resolved by checking 'show version | match "21.2R3-S8\|21.4R3-S6\|22.2R3-S4\|22.3R3-S3\|22.4R3\|23.2R2\|23.4R1-S1"'
Caveat Review Juniper Networks Junos OS Evolved upgrade guide for compatibility notes; ensure proper configuration backup before upgrade; some features may behave differently across major releases

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

Fix this in Junos Os Evolved Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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