CVE Vulnerabilities

CVE-2023-20241

Out-of-bounds Read

Published: Nov 22, 2023 | Modified: Jan 25, 2024
CVSS 3.x
5.5
MEDIUM
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

Multiple vulnerabilities in Cisco Secure Client Software, formerly AnyConnect Secure Mobility Client, could allow an authenticated, local attacker to cause a denial of service (DoS) condition on an affected system. These vulnerabilities are due to an out-of-bounds memory read from Cisco Secure Client Software. An attacker could exploit these vulnerabilities by logging in to an affected device at the same time that another user is accessing Cisco Secure Client on the same system, and then sending crafted packets to a port on that local host. A successful exploit could allow the attacker to crash the VPN Agent service, causing it to be unavailable to all users of the system. To exploit these vulnerabilities, the attacker must have valid credentials on a multi-user system.

Weakness

The product reads data past the end, or before the beginning, of the intended buffer.

Affected Software

Name Vendor Start Version End Version
Anyconnect_secure_mobility_client Cisco 4.9.00086 (including) 4.9.00086 (including)
Anyconnect_secure_mobility_client Cisco 4.9.01095 (including) 4.9.01095 (including)
Anyconnect_secure_mobility_client Cisco 4.9.02028 (including) 4.9.02028 (including)
Anyconnect_secure_mobility_client Cisco 4.9.03047 (including) 4.9.03047 (including)
Anyconnect_secure_mobility_client Cisco 4.9.03049 (including) 4.9.03049 (including)
Anyconnect_secure_mobility_client Cisco 4.9.04043 (including) 4.9.04043 (including)
Anyconnect_secure_mobility_client Cisco 4.9.04053 (including) 4.9.04053 (including)
Anyconnect_secure_mobility_client Cisco 4.9.05042 (including) 4.9.05042 (including)
Anyconnect_secure_mobility_client Cisco 4.9.06037 (including) 4.9.06037 (including)

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
  • To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.

References