CVE Vulnerabilities

CVE-2018-0158

Missing Release of Memory after Effective Lifetime

Published: Mar 28, 2018 | Modified: Jul 16, 2024
CVSS 3.x
8.6
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
CVSS 2.x
7.8 HIGH
AV:N/AC:L/Au:N/C:N/I:N/A:C
RedHat/V2
RedHat/V3
Ubuntu

A vulnerability in the Internet Key Exchange Version 2 (IKEv2) module of Cisco IOS Software and Cisco IOS XE Software could allow an unauthenticated, remote attacker to cause a memory leak or a reload of an affected device that leads to a denial of service (DoS) condition. The vulnerability is due to incorrect processing of certain IKEv2 packets. An attacker could exploit this vulnerability by sending crafted IKEv2 packets to an affected device to be processed. A successful exploit could cause an affected device to continuously consume memory and eventually reload, resulting in a DoS condition. Cisco Bug IDs: CSCvf22394.

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 Cisco 15.5(3)s1.1 (including) 15.5(3)s1.1 (including)
Ios Cisco 15.5(3)s1.2 (including) 15.5(3)s1.2 (including)
Ios Cisco 15.5(3)s1.4 (including) 15.5(3)s1.4 (including)
Ios Cisco 15.5(3)s1.5 (including) 15.5(3)s1.5 (including)
Ios Cisco 15.5(3)s1.7 (including) 15.5(3)s1.7 (including)
Ios Cisco 15.5(3)s1.8 (including) 15.5(3)s1.8 (including)
Ios Cisco 15.5(3)s1.9 (including) 15.5(3)s1.9 (including)
Ios Cisco 15.5(3)s1.10 (including) 15.5(3)s1.10 (including)
Ios Cisco 15.5(3)s1.11 (including) 15.5(3)s1.11 (including)
Ios Cisco 15.5(3)s1.12 (including) 15.5(3)s1.12 (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