CVE Vulnerabilities

CVE-2024-20304

Missing Release of Memory after Effective Lifetime

Published: Sep 11, 2024 | Modified: Oct 03, 2024
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

A vulnerability in the multicast traceroute version 2 (Mtrace2) feature of Cisco IOS XR Software could allow an unauthenticated, remote attacker to exhaust the UDP packet memory of an affected device.

This vulnerability exists because the Mtrace2 code does not properly handle packet memory. An attacker could exploit this vulnerability by sending crafted packets to an affected device. A successful exploit could allow the attacker to exhaust the incoming UDP packet memory. The affected device would not be able to process higher-level UDP-based protocols packets, possibly causing a denial of service (DoS) condition. Note: This vulnerability can be exploited using IPv4 or IPv6.

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
Ios_xr Cisco 7.7.1 (including) 7.7.1 (including)
Ios_xr Cisco 7.7.2 (including) 7.7.2 (including)
Ios_xr Cisco 7.7.21 (including) 7.7.21 (including)
Ios_xr Cisco 7.8.1 (including) 7.8.1 (including)
Ios_xr Cisco 7.8.2 (including) 7.8.2 (including)
Ios_xr Cisco 7.8.12 (including) 7.8.12 (including)
Ios_xr Cisco 7.8.22 (including) 7.8.22 (including)
Ios_xr Cisco 7.9.1 (including) 7.9.1 (including)
Ios_xr Cisco 7.9.2 (including) 7.9.2 (including)
Ios_xr Cisco 7.9.21 (including) 7.9.21 (including)
Ios_xr Cisco 7.10.1 (including) 7.10.1 (including)
Ios_xr Cisco 7.10.2 (including) 7.10.2 (including)
Ios_xr Cisco 7.11.1 (including) 7.11.1 (including)
Ios_xr Cisco 7.11.2 (including) 7.11.2 (including)
Ios_xr Cisco 24.1.1 (including) 24.1.1 (including)
Ios_xr Cisco 24.1.2 (including) 24.1.2 (including)
Ios_xr Cisco 24.2.1 (including) 24.2.1 (including)
Ios_xr Cisco 24.2.11 (including) 24.2.11 (including)

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