CVE-2023-28980

A Use After Free vulnerability in the routing protocol daemon of Juniper Networks Junos OS and Junos OS Evolved allows a locally authenticated attacker with low privileges to cause Denial of Service (DoS). In a rib sharding scenario the rpd process will crash shortly after specific CLI command is issued. This issue is more likely to occur in a scenario with high route scale (>1M routes).

This issue affects: Juniper Networks Junos OS

• 20.2 version 20.2R3-S5 and later versions prior to 20.2R3-S6;
• 20.3 version 20.3R3-S2 and later versions prior to 20.3R3-S5;
• 20.4 version 20.4R3-S1 and later versions prior to 20.4R3-S4
• 21.1 version 21.1R3 and later versions prior to 21.1R3-S3;
• 21.2 version 21.2R1-S2, 21.2R2-S1 and later versions prior to 21.2R3-S2;
• 21.3 version 21.3R2 and later versions prior to 21.3R3;
• 21.4 versions prior to 21.4R2-S1, 21.4R3;
• 22.1 versions prior to 22.1R2.

Juniper Networks Junos OS Evolved

• 20.4-EVO version 20.4R3-S1-EVO and later versions prior to 20.4R3-S6-EVO;
• 21.2-EVO version 21.2R1-S2-EVO and later versions prior to 21.2R3-S4-EVO;
• 21.3-EVO version 21.3R2-EVO and later versions prior to 21.3R3-S1-EVO;
• 21.4-EVO versions prior to 21.4R2-S1-EVO, 21.4R3-EVO;
• 22.1-EVO versions prior to 22.1R2-EVO.

Weakness

Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code.

Affected Software

Extended Description

The use of previously-freed memory can have any number of adverse consequences, ranging from the corruption of valid data to the execution of arbitrary code, depending on the instantiation and timing of the flaw. The simplest way data corruption may occur involves the system’s reuse of the freed memory. Use-after-free errors have two common and sometimes overlapping causes:

In this scenario, the memory in question is allocated to another pointer validly at some point after it has been freed. The original pointer to the freed memory is used again and points to somewhere within the new allocation. As the data is changed, it corrupts the validly used memory; this induces undefined behavior in the process. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Potential Mitigations

References

• https://supportportal.juniper.net/JSA70606