CVE-2023-22392

Junos OS: PTX Series and QFX10000 Series: Received flow-routes which aren't installed as the hardware doesn't support them, lead to an FPC heap memory leak

MEDIUM
6.5
CVSS Score
Published: October 12, 2023 at 10:55 PM UTC
Updated: June 17, 2026 at 05:35 AM UTC
11 products affected across 2 vendorsJunosPtx10008Ptx10004

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.3%

Description

A Missing Release of Memory after Effective Lifetime vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS allows an adjacent, unauthenticated attacker to cause a Denial of Service (DoS). PTX3000, PTX5000, QFX10000, PTX1000, PTX10002, and PTX10004, PTX10008 and PTX10016 with LC110x FPCs do not support certain flow-routes. Once a flow-route is received over an established BGP session and an attempt is made to install the resulting filter into the PFE, FPC heap memory is leaked. The FPC heap memory can be monitored using the CLI command "show chassis fpc". The following syslog messages can be observed if the respective filter derived from a flow-route cannot be installed. expr_dfw_sfm_range_add:661 SFM packet-length Unable to get a sfm entry for updating the hw expr_dfw_hw_sfm_add:750 Unable to add the filter secondarymatch to the hardware expr_dfw_base_hw_add:52 Failed to add h/w sfm data. expr_dfw_base_hw_create:114 Failed to add h/w data. expr_dfw_base_pfe_inst_create:241 Failed to create base inst for sfilter 0 on PFE 0 for __flowspec_default_inet__ expr_dfw_flt_inst_change:1368 Failed to create __flowspec_default_inet__ on PFE 0 expr_dfw_hw_pgm_fnum:465 dfw_pfe_inst_old not found for pfe_index 0! expr_dfw_bp_pgm_flt_num:548 Failed to pgm bind-point in hw: generic failure expr_dfw_bp_topo_handler:1102 Failed to program fnum. expr_dfw_entry_process_change:679 Failed to change instance for filter __flowspec_default_inet__. This issue affects Juniper Networks Junos OS: on PTX1000, PTX10002, and PTX10004, PTX10008 and PTX10016 with LC110x FPCs: * All versions prior to 20.4R3-S5; * 21.1 versions prior to 21.1R3-S4; * 21.2 versions prior to 21.2R3-S2; * 21.3 versions prior to 21.3R3; * 21.4 versions prior to 21.4R2-S2, 21.4R3; * 22.1 versions prior to 22.1R1-S2, 22.1R2. on PTX3000, PTX5000, QFX10000: * All versions prior to 20.4R3-S8; * 21.1 version 21.1R1 and later versions; * 21.2 versions prior to 21.2R3-S6; * 21.3 versions prior to 21.3R3-S5; * 21.4 versions prior to 21.4R3-S4; * 22.1 versions prior to 22.1R3-S3 * 22.2 versions prior to 22.2R3-S1 * 22.3 versions prior to 22.3R2-S2, 22.3R3 * 22.4 versions prior to 22.4R2.

Affected

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

Affected range stops below 20.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.4R3-S5, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.4R3-S8, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.1*, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.1R3-S4, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.2R3-S2, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.2R3-S6, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.3R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.3R3-S5, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.4R2-S2, 21.4R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.4R3-S4, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.1R1-S2, 22.1R2, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.1R3-S3, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.2R3-S1, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.3R2-S2, 22.3R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.4R2, so it looks safe — our inference, not a vendor statement
juniper-ptx1000 (environment) · juniper-ptx1000-72q (environment) · juniper-ptx10002 (environment) · juniper-ptx10002-60c (environment) · juniper-ptx10004 (environment) · juniper-ptx10008 (environment) · juniper-ptx10016 (environment) · juniper-ptx3000 (environment) · juniper-ptx5000 (environment) · juniper-qfx10000 (environment)
All versions
All versions
All versions
All versions
All versions
All versions
All versions
All versions
All versions

Remediation

No guide yet

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

Patch and advisory references

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

StatusMODIFIED
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