CVE Vulnerabilities

CVE-2023-28982

Missing Release of Memory after Effective Lifetime

Published: Apr 17, 2023 | Modified: May 02, 2023
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

A Missing Release of Memory after Effective Lifetime vulnerability in the routing protocol daemon of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network based attacker to cause a Denial of Service (DoS). In a BGP rib sharding scenario, when an attribute of an active BGP route is updated memory will leak. As rpd memory usage increases over time the rpd process will eventually run out of memory, crash, and restart. The memory utilization can be monitored with the following CLI commands: show task memory show system processes extensive | match rpd This issue affects: Juniper Networks Junos OS 20.3 versions prior to 20.3R3-S2; 20.4 versions prior to 20.4R3-S6; 21.1 versions prior to 21.1R3; 21.2 versions prior to 21.2R3; 21.3 versions prior to 21.3R2. Juniper Networks Junos OS Evolved 20.3-EVO version 20.3R1-EVO and later versions; 20.4-EVO versions prior to 20.4R3-S6-EVO; 21.2-EVO versions prior to 21.2R3-EVO; 21.3-EVO versions prior to 21.3R2-EVO.

Weakness

The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory.

Affected Software

Name Vendor Start Version End Version
Junos Juniper 20.3 20.3
Junos Juniper 20.3 20.3
Junos Juniper 20.3 20.3
Junos Juniper 20.3 20.3
Junos Juniper 20.3 20.3
Junos Juniper 20.3 20.3
Junos Juniper 20.3 20.3
Junos Juniper 20.3 20.3
Junos Juniper 20.4 20.4
Junos Juniper 20.4 20.4
Junos Juniper 20.4 20.4
Junos Juniper 20.4 20.4
Junos Juniper 20.4 20.4
Junos Juniper 20.4 20.4
Junos Juniper 20.4 20.4
Junos Juniper 20.4 20.4
Junos Juniper 20.4 20.4
Junos Juniper 20.4 20.4
Junos Juniper 20.4 20.4
Junos Juniper 20.4 20.4
Junos Juniper 21.1 21.1
Junos Juniper 21.1 21.1
Junos Juniper 21.1 21.1
Junos Juniper 21.1 21.1
Junos Juniper 21.1 21.1
Junos Juniper 21.1 21.1
Junos Juniper 21.2 21.2
Junos Juniper 21.2 21.2
Junos Juniper 21.2 21.2
Junos Juniper 21.2 21.2
Junos Juniper 21.2 21.2
Junos Juniper 21.2 21.2
Junos Juniper 21.2 21.2
Junos Juniper 21.3 21.3
Junos Juniper 21.3 21.3
Junos Juniper 21.3 21.3
Junos Juniper 21.3 21.3

Potential Mitigations

  • Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone.
  • For example, glibc in Linux provides protection against free of invalid pointers.
  • When using Xcode to target OS X or iOS, enable automatic reference counting (ARC) [REF-391].
  • To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std::auto_ptr (defined by ISO/IEC ISO/IEC 14882:2003), std::shared_ptr and std::unique_ptr (specified by an upcoming revision of the C++ standard, informally referred to as C++ 1x), or equivalent solutions such as Boost.

References