CVE intelligence and bounded remediation

CVE-2023-20241 — Cisco Anyconnect Secure Mobility Client security vulnerability

Medium CVSS 5.5

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.

Severity
Medium
CVSS
5.5 (3.1)
Published
2023-11-22
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-125

Affected products

  • cisco / anyconnect_secure_mobility_client / 4.9.00086
  • cisco / anyconnect_secure_mobility_client / 4.9.01095
  • cisco / anyconnect_secure_mobility_client / 4.9.02028
  • cisco / anyconnect_secure_mobility_client / 4.9.03047
  • cisco / anyconnect_secure_mobility_client / 4.9.03049
  • cisco / anyconnect_secure_mobility_client / 4.9.04043

Showing 6 representative product identities from 30 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Buffer bounds, memory safety, and memory corruption

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Identify affected native-code versions, build flags, architectures, parsers, codecs, drivers, and input paths in all shipped artifacts.
  • Determine whether untrusted data reaches the affected routine and the process privilege, sandbox, and network exposure.
  • Confirm statically linked, vendored, firmware, and platform-provided copies, not only package-manager records.

Remediate safely

  • Apply the maintained upstream correction or replace the affected component, then rebuild every dependent artifact from clean inputs.
  • Adopt bounds-checked interfaces, validated sizes and integer conversions, clear ownership, and memory-safe components where practical.
  • Enable supported compiler and runtime hardening and add sanitized tests and fuzz regression seeds derived from non-weaponized fixtures.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.