CVE-2024-47499: In a BMP scenario receipt of a malformed AS PATH attribute can cause an RPD crash

Automatic summary from the vendor's CVE record. We haven't written a full analysis of this vulnerability yet.

Affected and fixed versions

Product / branch	Fixed in
Junos OS 0	21.2R3-S8 or later
Junos OS 21.4	21.4R3-S8 or later
Junos OS 22.2	22.2R3-S4 or later
Junos OS 22.3	22.3R3-S3 or later
Junos OS 22.4	22.4R3-S2 or later
Junos OS 23.2	23.2R2-S1 or later
Junos OS 23.4	23.4R1-S2, 23.4R2 or later
Junos OS Evolved 0	21.2R3-S8-EVO or later
Junos OS Evolved 21.4	21.4R3-S8-EVO or later
Junos OS Evolved 22.2	22.2R3-S4-EVO or later
Junos OS Evolved 22.3	22.3R3-S3-EVO or later
Junos OS Evolved 22.4	22.4R3-S2-EVO or later
Junos OS Evolved 23.2	23.2R2-S1-EVO or later
Junos OS Evolved 23.4	23.4R1-S2-EVO, 23.4R2-EVO or later

Always confirm against the vendor advisory, which lists every fixed hotfix.

What it is

An Improper Check for Unusual or Exceptional Conditions vulnerability in the routing protocol daemon (RPD) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network based attacker to cause a Denial of Service (DoS).

In a scenario where BGP Monitoring Protocol (BMP) is configured with rib-in pre-policy monitoring, receiving a BGP update with a specifically malformed AS PATH attribute over an established BGP session, can cause an RPD crash and restart.

This issue affects:

Junos OS:

All versions before 21.2R3-S8,
21.4 versions before 21.4R3-S8,
22.2 versions before 22.2R3-S4,
22.3 versions before 22.3R3-S3,
22.4 versions before 22.4R3-S2,
23.2 versions before 23.2R2-S1,
23.4 versions before 23.4R1-S2, 23.4R2;

Junos OS Evolved:

All versions before 21.2R3-S8-EVO,
21.4 versions before 21.4R3-S8-EVO,
22.2 versions before 22.2R3-S4-EVO,
22.3 versions before 22.3R3-S3-EVO,
22.4 versions before 22.4R3-S2-EVO,
23.2 versions before 23.2R2-S1-EVO,
23.4 versions before 23.4R1-S2-EVO, 23.4R2-EVO.

Am I affected?

To be exposed to this issue pre-policy for BMP needs to be configured at least once: [ protocols bgp ... bmp route-monitoring pre-policy ] or

[ routing-options bmp ... route-monitoring pre-policy ]

Workarounds

As a work-around, the "exclude-non-feasible" knob can be configured to prevent the crash at:

[ protocols bgp ... bmp route-monitoring pre-policy exclude-non-feasible ]

[ routing-options bmp ... route-monitoring pre-policy exclude-non-feasible ]

depending on where pre-policy is configured.

Exploitation

Juniper SIRT is not aware of any malicious exploitation of this vulnerability.

KEV status, EPSS score and vendor data refreshed automatically, last on 13 Oct 2026.