CVE-2024-47493

Junos OS: MX Series: Trio-based FPCs: Continuous physical Interface flaps causes local FPC to crash

MEDIUM
6.5
CVSS Score
Published: October 11, 2024 at 03:24 PM UTC
Updated: June 17, 2026 at 07:57 AM UTC
1 product affected across 1 vendorJunos

Using Junos OS by Juniper Networks?

Get instant alerts when new vulnerabilities affect Junos OS - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.5
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Affected range stops below 21.2R3-S7, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.4R3-S6, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.1R3-S5, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.2R3-S3, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.3R3-S2, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.4R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.2R2, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.4R2, so it looks safe — our inference, not a vendor statement
juniper-mx10004 (environment) · juniper-mx10008 (environment) · juniper-mx2008 (environment) · juniper-mx2010 (environment) · juniper-mx2020 (environment) · juniper-mx204 (environment) · juniper-mx240 (environment) · juniper-mx304 (environment) · juniper-mx480 (environment) · juniper-mx960 (environment)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.5MEDIUMjuniper
Attack Vector
ADJACENT_NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-401

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card