CVE-2024-39541: Inconsistent information in the TE database can lead 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 22.4	22.4R3-S1 or later
Junos OS 23.2	23.2R2 or later
Junos OS 23.4	23.4R1-S1, 23.4R2 or later
Junos OS 0	Not affected
Junos OS Evolved 22.4-EVO	22.4R3-S2-EVO or later
Junos OS Evolved 23.2-EVO	23.2R2-EVO or later
Junos OS Evolved 23.4-EVO	23.4R1-S1-EVO, 23.4R2-EVO or later
Junos OS Evolved 0	Not affected

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 an unauthenticated, adjacent attacker to cause a Denial-of-Service (DoS).

When conflicting information (IP or ISO addresses) about a node is added to the Traffic Engineering (TE) database and then a subsequent operation attempts to process these, rpd will crash and restart.

This issue affects:

Junos OS:

22.4 versions before 22.4R3-S1,
23.2 versions before 23.2R2,
23.4 versions before 23.4R1-S1, 23.4R2,

This issue does not affect Junos OS versions earlier than 22.4R1.

Junos OS Evolved:

22.4-EVO versions before 22.4R3-S2-EVO,
23.2-EVO versions before 23.2R2-EVO,
23.4-EVO versions before 23.4R1-S1-EVO, 23.4R2-EVO,

This issue does not affect Junos OS Evolved versions earlier than

before 22.4R1.

Am I affected?

To be exposed to this issue traffic engineering per:

[ protocols source-packet-routing traffic-engineering database ]

and either OSPF or ISIS TE per:

[ protocols ospf traffic-engineering ] or [ protocols isis traffic-engineering ]

have to be configured.

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.