dbcve.org
JunosOperating system · Juniper

CVE-2024-47493

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-11
Fix available
A fix is available. Upgrade to 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
A Missing Release of Memory after Effective Lifetime vulnerability in the Packet Forwarding Engine (PFE) of the Juniper Networks Junos OS on the MX Series platforms with Trio-based FPCs allows an unauthenticated, adjacent attacker to cause a Denial of Service (DoS). In case of channelized Modular Interface Cards (MICs), every physical interface flap operation will leak heap memory. Over a period of time, continuous physical interface flap operations causes local FPC to eventually run out of memory and crash.   Below CLI command can be used to check the memory usage over a period of time:   user@host> show chassis fpc                 Temp CPU Utilization (%)   CPU Utilization (%) Memory   Utilization (%)   Slot State     (C)  Total  Interrupt     1min   5min   15min DRAM (MB) Heap     Buffer   0 Online       43     41         2                           2048       49         14   1 Online       43     41         2                           2048       49         14   2 Online       43     41         2                           2048       49         14 This issue affects Junos OS on MX Series:  * All versions before 21.2R3-S7,  * from 21.4 before 21.4R3-S6,  * from 22.1 before 22.1R3-S5,  * from 22.2 before 22.2R3-S3,  * from 22.3 before 22.3R3-S2,  * from 22.4 before 22.4R3,  * from 23.2 before 23.2R2,  * 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

Memory leak vulnerability in the Packet Forwarding Engine (PFE) on Juniper MX Series platforms with Trio-based FPCs. When channelized MICs experience physical interface flap operations, heap memory is leaked each time. Over sustained interface flapping, memory exhaustion causes the local FPC to crash, resulting in Denial of Service.

MitigationUpgrade Junos OS to the fixed versions (21.2R3-S7, 21.4R3-S6, 22.1R3-S5, 22.2R3-S3, 22.3R3-S2, 22.4R3, 23.2R2, or 23.4R2 and later). Monitor FPC memory utilization using 'show chassis fpc' to detect abnormal heap growth indicative of the leak.

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.2= 21.2= 21.4= 22.1= 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. Identify MX Series hardware with Trio-based FPCs
    Run 'show chassis hardware' and look for MX Series routers with FPCs that include Trio chipsets (typically MPC/MIC cards).
    Affected if The device is an MX Series router with Trio-based FPCs (MPC line cards).
  2. Verify Junos OS version is within affected range
    Run 'show version' and compare the installed Junos version against: < 21.2, 21.2, 21.4, 22.1, 22.2, 22.3, 22.4, 23.2, or 23.4.
    Affected if The installed Junos version matches any of the listed affected versions.
  3. Confirm channelized MICs are in use
    Run 'show interfaces terse' or 'show chassis fpc pic-status' to identify if channelized MICs (channelized SONET/SDH or channelized Ethernet interfaces) are configured and active.
    Affected if Channelized MICs are present and configured on the Trio-based FPC.
  4. Monitor FPC heap memory for growth
    Run 'show chassis fpc' repeatedly over time and observe the Heap Memory Utilized field for each FPC. Compare values over several hours or days.
    Affected if Heap memory utilization shows continuous growth without returning to baseline, indicating a leak.
  5. Check for physical interface flaps on channelized interfaces
    Run 'show interface statistics' on channelized interfaces to count flap events, or review system logs for interface flap messages.
    Affected if Frequent physical interface flaps are occurring on channelized MIC interfaces.

If the device is an MX Series with Trio-based FPCs, runs an affected Junos version, uses channelized MICs, and shows increasing heap memory on the FPC following interface flaps, the environment is likely affected by this CVE.

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.2 or later
Fixed in 21.2
Interim mitigation

Upgrade Junos OS to the fixed versions (21.2R3-S7, 21.4R3-S6, 22.1R3-S5, 22.2R3-S3, 22.3R3-S2, 22.4R3, 23.2R2, or 23.4R2 and later). Monitor FPC memory utilization using 'show chassis fpc' to detect abnormal heap growth indicative of the leak.

Recommended fix High confidence

21.2R3-S7, 21.4R3-S6, 22.1R3-S5, 22.2R3-S3, 22.3R3-S2, 22.4R3, 23.2R2, or 23.4R2 (depending on which version branch you are upgrading from)

  1. 1. Identify the current Junos OS version running on the MX Series device using: show version
  2. 2. Determine which version branch your current code falls into (21.2, 21.4, 22.1, 22.2, 22.3, 22.4, 23.2, or 23.4)
  3. 3. Schedule a maintenance window for the upgrade procedure
  4. 4. Download the appropriate fixed release for your version branch from Juniper Networks support portal
  5. 5. Upload the Junos OS upgrade package to the device using: file copy or USB transfer
  6. 6. Install the upgrade using: request system software add <package> reboot
  7. 7. After reboot, verify the new version using: show version
  8. 8. Monitor memory utilization over time using: show chassis fpc to confirm the memory leak is resolved
Caveat Standard Junos OS upgrade considerations apply - review release notes for any configuration changes or compatibility notices before upgrading

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

Fix this in Junos Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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