dbcve.org
Junos Os EvolvedOperating system · Juniper

CVE-2024-47489

MEDIUM · 5.8 CVSS v3.1 Published 2024-10-11
Fix available
A fix is available. Upgrade to 21.4 or later.
See remediation →
67/100
Remediation priority · Elevated
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 Handling of Exceptional Conditions vulnerability in the Packet Forwarding Engine (pfe) of the Juniper Networks Junos OS Evolved on ACX Series devices allows an unauthenticated, network based attacker sending specific transit protocol traffic to cause a partial Denial of Service (DoS) to downstream devices. Receipt of specific transit protocol packets is incorrectly processed by the Routing Engine (RE), filling up the DDoS protection queue which is shared between routing protocols. This influx of transit protocol packets causes DDoS protection violations, resulting in protocol flaps which can affect connectivity to networking devices. This issue affects both IPv4 and IPv6. This issue does not require any specific routing protocol to be configured or enabled. The following commands can be used to monitor the DDoS protection queue:        labuser@re0> show evo-pfemand host pkt-stats     labuser@re0> show host-path ddos all-policers This issue affects Junos OS Evolved:  * All versions before 21.4R3-S8-EVO,  * from 22.2 before 22.2R3-S4-EVO,  * from 22.3 before 22.3R3-S4-EVO,  * from 22.4 before 22.4R3-S3-EVO,  * from 23.2 before 23.2R2-EVO,  * from 23.4 before 23.4R1-S1-EVO, 23.4R2-EVO,  * from 24.2 before 24.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

A vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS Evolved on ACX Series allows an unauthenticated remote attacker sending specific transit protocol packets to cause incorrect processing by the Routing Engine, filling the shared DDoS protection queue and triggering protection violations that cause protocol flaps and downstream DoS.

MitigationApply the appropriate Junos OS Evolved software update from the fixed versions list (21.4R3-S8-EVO, 22.2R3-S4-EVO, 22.3R3-S4-EVO, 22.4R3-S3-EVO, 23.2R2-EVO, 23.4R1-S1-EVO/23.4R2-EVO, or 24.2R2-EVO) to address the improper handling of exceptional conditions in the PFE.

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= 24.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
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L

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 platform
    Run 'show chassis hardware' and 'show version' commands to confirm the device is an ACX Series running Junos OS Evolved
    Affected if Device is ACX Series AND running Junos OS Evolved
  2. Check installed Junos OS Evolved version
    Execute 'show version' and compare the output version number against the affected list: any version <21.4, 21.4, 22.2, 22.3, 22.4, 23.2, 23.4, or 24.2
    Affected if Installed version matches one of the affected version numbers in the list
  3. Verify the device processes transit protocol traffic
    Review interface statistics and traffic logs for transit protocol packets (such as BGP, OSPF, or other routing protocols) passing through the PFE
    Affected if Device processes transit routing protocol traffic on ACX Series hardware
  4. Check for DDoS protection violations
    Run 'show ddos protection statistics' to inspect for protection violations, especially on the shared queue, and look for protocol flap messages in system logs
    Affected if DDoS protection violations are present or protocol flaps are occurring on the Routing Engine

The environment is affected if the device is an ACX Series running Junos OS Evolved with a version matching the affected list AND the device processes transit protocol traffic, which can trigger the PFE vulnerability.

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 appropriate Junos OS Evolved software update from the fixed versions list (21.4R3-S8-EVO, 22.2R3-S4-EVO, 22.3R3-S4-EVO, 22.4R3-S3-EVO, 23.2R2-EVO, 23.4R1-S1-EVO/23.4R2-EVO, or 24.2R2-EVO) to address the improper handling of exceptional conditions in the PFE.

Recommended fix High confidence

21.4R3-S8-EVO, 22.2R3-S4-EVO, 22.3R3-S4-EVO, 22.4R3-S3-EVO, 23.2R2-EVO, 23.4R1-S1-EVO, 23.4R2-EVO, or 24.2R2-EVO (choose the branch matching your current version and upgrade to the latest available in that branch)

  1. 1. Identify the current Junos OS Evolved version running on the ACX Series device using 'show version'
  2. 2. Determine which upgrade path applies based on the current version (see upgrade_path for fixed releases)
  3. 3. Download the appropriate fixed Junos OS Evolved image from the Juniper Networks support portal (supportportal.juniper.net)
  4. 4. Transfer the image to the device using 'file copy' or similar method
  5. 5. Install the upgrade using 'request system software add <package>' with the appropriate options (e.g., no-validate, reboot)
  6. 6. After reboot, verify the new version is running with 'show version'
  7. 7. Monitor DDoS protection statistics using 'show evo-pfemand host pkt-stats' and 'show host-path ddos all-policers' to confirm the issue is resolved
  8. 8. Verify normal protocol operation and connectivity
Caveat Review Junos OS Evolved release notes for any compatibility notes or configuration changes between your current version and the target version before upgrading

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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