dbcve.org
Junos Os EvolvedOperating system · Juniper

CVE-2024-47490

HIGH · 8.2 CVSS v3.1 Published 2024-10-11
Fix available
A fix is available. Upgrade to 21.4 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable 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 Restriction of Communication Channel to Intended Endpoints vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS Evolved on ACX 7000 Series allows an unauthenticated, network based attacker to cause increased consumption of resources, ultimately resulting in a Denial of Service (DoS). When specific transit MPLS packets are received by the PFE, these packets are internally forwarded to the Routing Engine (RE), rather than being handled appropriately. Continuous receipt of these MPLS packets causes resources to be exhausted. MPLS config is not required to be affected by this issue.  This issue affects Junos OS Evolved ACX 7000 Series:  * All versions before 21.4R3-S9-EVO, * 22.2-EVO before 22.2R3-S4-EVO,  * 22.3-EVO before 22.3R3-S3-EVO,  * 22.4-EVO before 22.4R3-S2-EVO,  * 23.2-EVO before 23.2R2-EVO,  * 23.4-EVO before 23.4R1-S1-EVO, 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 vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS Evolved on ACX 7000 Series allows an unauthenticated attacker to cause resource exhaustion and DoS. When specific transit MPLS packets are received by the PFE, they are incorrectly forwarded to the Routing Engine (RE) instead of being handled appropriately by the PFE, causing increased resource consumption until services fail.

MitigationApply the vendor-supplied patches for all affected versions. As an interim measure, consider implementing network segmentation or access controls to limit exposure to unauthenticated network-based attackers sending the specific MPLS packets.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 device model and software
    Run 'show chassis hardware' and 'show version' to confirm the device is an ACX 7000 Series running Junos OS Evolved
    Affected if Device is ACX 7000 Series with Junos OS Evolved installed
  2. Check installed Junos OS Evolved version
    Run 'show version' and compare the software version to the affected list: < 21.4, 21.4, 22.2, 22.3, 22.4, 23.2, or 23.4
    Affected if Installed version matches any of the listed affected versions
  3. Verify MPLS configuration
    Run 'show configuration protocols mpls' to check if MPLS protocol is enabled on the device
    Affected if MPLS is configured and active on the device
  4. Check for symptoms of resource exhaustion
    Run 'show system processes extensive' and 'show system memory' to monitor Routing Engine resource consumption; look for unusually high CPU or memory usage on the RE
    Affected if Routing Engine shows abnormally high resource consumption without other explaining traffic patterns

Device is affected if it is an ACX 7000 Series running Junos OS Evolved with an affected version AND has MPLS enabled, showing signs of RE resource exhaustion from transit MPLS traffic.

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.4 or later
Fixed in 21.4
Interim mitigation

Apply the vendor-supplied patches for all affected versions. As an interim measure, consider implementing network segmentation or access controls to limit exposure to unauthenticated network-based attackers sending the specific MPLS packets.

Recommended fix High confidence

Upgrade to 23.4R2-EVO (or latest available fixed release for your branch: 21.4R3-S9-EVO, 22.2R3-S4-EVO, 22.3R3-S3-EVO, 22.4R3-S2-EVO, or 23.2R2-EVO)

  1. Identify the current Junos OS Evolved version on the ACX 7000 Series device using 'show version' command
  2. Based on current version, upgrade to one of the fixed releases: 21.4R3-S9-EVO, 22.2R3-S4-EVO, 22.3R3-S3-EVO, 22.4R3-S2-EVO, 23.2R2-EVO, or 23.4R2-EVO (preferred)
  3. Download the appropriate Junos OS Evolved image from the Juniper Networks support portal (supportportal.juniper.net)
  4. Upload the new image to the device using 'request system software add' command with appropriate options
  5. Reboot the device after successful software installation using 'request system reboot' command
  6. Verify the new version is running with 'show version' and confirm the vulnerability is remediated
Caveat Standard Junos OS upgrade considerations apply - verify hardware compatibility, review release notes for behavioral changes, and plan for maintenance window as upgrade requires reboot

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

Fix this in Junos Os Evolved Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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