2024-07 Security Bulletin: Junos OS and Junos OS Evolved: Inconsistent information in the TE database can lead to an rpd crash (CVE-2024-39541)

Product Affected

This issue affects Junos OS 22.4, 23.2, 23.4; and Junos OS Evolved 22.4-EVO, 23.2-EVO, 23.4-EVO; on all platforms.

Severity

Medium

Severity Assessment (CVSS) Score

CVSS 3.1: 6.5 (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)

CVSS 4.0: 7.1 (CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L)

Problem

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.

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.

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

This issue was found during internal product security testing or research.

Solution

The following software releases have been updated to resolve this specific issue:
Junos OS: 22.4R3-S1, 23.2R2, 23.4R1-S1, 23.4R2, 24.2R1, and all subsequent releases;
Junos OS Evolved: 22.4R3-S2-EVO, 23.2R2-EVO, 23.4R1-S1-EVO, 23.4R2-EVO, 24.2R1-EVO, and all subsequent releases.

This issue is being tracked as 1759082 which is visible on the Customer Support website.

Note: Juniper SIRT's policy is not to evaluate releases which are beyond End of Engineering (EOE) or End of Life (EOL).

Workaround

There are no known workarounds for this issue.

Severity Assessment

Information for how Juniper Networks uses CVSS can be found at KB 16446 [juniper.net] "Common Vulnerability Scoring System (CVSS) and Juniper's Security Advisories."

Modification History