dbcve.org
JunosOperating system · Juniper

CVE-2024-47496

MEDIUM · 5.5 CVSS v3.1 Published 2024-10-11
Fix available
A fix is available. Upgrade to 21.4 or later.
See remediation →
57/100
Remediation priority · Elevated
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 NULL Pointer Dereference vulnerability in the Packet Forwarding Engine (pfe) of Juniper Networks Junos OS allows a local, low-privileged attacker to cause a Denial-of-Service (DoS). When a specific command is executed, the pfe crashes. This will cause traffic forwarding to be interrupted until the system self-recovers. Repeated execution will create a sustained DoS condition. This issue only affects MX Series devices with Line cards MPC1-MPC9. This issue affects: Junos OS on MX Series: * All versions before 21.4R3-S9, * from 22.2 before 22.2R3-S5,  * from 22.3 before 22.3R3-S4, * from 22.4 before 22.4R3-S2, * from 23.2 before 23.2R2-S1, * from 23.4 before 23.4R2.

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 NULL pointer dereference vulnerability exists in the Packet Forwarding Engine (pfe) of Juniper Networks Junos OS on MX Series devices with MPC1-MPC9 line cards. A local, low-privileged attacker can trigger the vulnerability by executing a specific command, causing the pfe to crash and interrupting traffic forwarding until system self-recovery. Repeated exploitation results in sustained DoS.

MitigationUpgrade Junos OS to the fixed versions (21.4R3-S9, 22.2R3-S5, 22.3R3-S4, 22.4R3-S2, 23.2R2-S1, or 23.4R2 or later) for affected MX Series devices with MPC line cards.

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

CVSS:3.1/AV:L/AC:L/PR:L/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 device is MX Series
    Run 'show version' or 'show chassis hardware' to identify the device platform
    Affected if Device is not an MX Series router - not affected
  2. Verify MPC line card presence
    Execute 'show chassis hardware' or 'show pic slot' to determine if MPC1 through MPC9 line cards are installed
    Affected if No MPC line cards present - not affected
  3. Check Junos OS version
    Run 'show version' to obtain the installed Junos OS version number
    Affected if Version matches 21.4, 22.2, 22.3, 22.4, 23.2, or 23.4, or any version below 21.4 - potentially affected
  4. Confirm pfe is operational
    Run 'show pfe statistics' or check that the Packet Forwarding Engine process is running
    Affected if pfe is running on an affected MX Series with MPC - vulnerable to the specific command trigger

Device is affected if it is an MX Series router with MPC1-MPC9 line cards running Junos OS versions 21.4 through 23.4 (excluding the patched releases)

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

Upgrade Junos OS to the fixed versions (21.4R3-S9, 22.2R3-S5, 22.3R3-S4, 22.4R3-S2, 23.2R2-S1, or 23.4R2 or later) for affected MX Series devices with MPC line cards.

Recommended fix High confidence

Upgrade to the minimum fixed version for your current branch: 21.4R3-S9, 22.2R3-S5, 22.3R3-S4, 22.4R3-S2, 23.2R2-S1, or 23.4R2 (whichever applies to your current version)

  1. 1. Identify the current Junos OS version running on the MX Series device using 'show version'
  2. 2. Based on current version, determine the minimum fixed release needed (21.4R3-S9, 22.2R3-S5, 22.3R3-S4, 22.4R3-S2, 23.2R2-S1, or 23.4R2)
  3. 3. Download the appropriate Junos OS upgrade package from the Juniper support portal
  4. 4. Before upgrading, backup the current configuration using 'request system configuration backup'
  5. 5. Upload the upgrade package to the device using 'request system software add <package> reboot'
  6. 6. After reboot, verify the new version is installed using 'show version'
  7. 7. Verify the fix is applied by confirming the pfe no longer crashes when the specific command is executed
  8. 8. Monitor the system to ensure stable operation
Caveat Standard Junos upgrade considerations apply - review release notes for any command syntax changes or feature modifications before upgrading

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

Fix this in Junos 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-47496 — 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-47496 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