CVE-2024-47491: Receipt of a specific malformed BGP path attribute leads to 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.4R3-S8 or later
Junos OS 22.2	22.2R3-S4 or later
Junos OS 22.4	22.4R3-S3 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.4R3-S8-EVO or later
Junos OS Evolved 22.2	22.2R3-S4-EVO or later
Junos OS Evolved 22.4	22.4R3-S3-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 Handling of Exceptional Conditions vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows a network-based, unauthenticated attacker to cause Denial of Service (DoS).

When a BGP UPDATE with malformed path attribute is received over an established BGP session, rpd crashes and restarts.

Continuous receipt of a BGP UPDATE with a specifically malformed path attribute will create a sustained Denial of Service (DoS) condition for impacted devices. While this issue affects systems running 32-bit and 64-bit systems, the probability of impact on 64-bit system is extremely low. According to KB25803 https://supportportal.juniper.net/s/article/Junos-How-to-check-if-Junos-OS-is-64-or-32-bit-on-a-router , customers can confirm 32-bit or 64-bit system via the ' show version detail ' command:

lab@router> show version detail| match 32 JUNOS 32-bit kernel Software Suite

lab@router> show version detail| match 64 JUNOS 64-bit kernel Software Suite

This issue affects:

Juniper Networks Junos OS:

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

Juniper Networks Junos OS Evolved: * All versions before 21.4R3-S8-EVO, * from 22.2 before 22.2R3-S4-EVO, * from 22.4 before 22.4R3-S3-EVO, * from 23.2 before 23.2R2-S1-EVO, * from 23.4 before 23.4R1-S2-EVO, 23.4R2-EVO.

Am I affected?

To be exposed to this issue a minimal BGP configuration like the following is required:

[ protocols bgp group <name> neighbor ... ]

Workarounds

There are no known workarounds for this issue.

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.