CVE intelligence and bounded remediation

CVE-2024-20299 — Cisco Adaptive Security Appliance Software security vulnerability

Medium CVSS 5.8

A vulnerability in the AnyConnect firewall for Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to bypass a configured access control list (ACL) and allow traffic that should have been denied to flow through an affected device. This vulnerability is due to a logic error in populating group ACLs when an AnyConnect client establishes a new session toward an affected device. An attacker could exploit this vulnerability by establishing an AnyConnect connection to the affected device. A successful exploit could allow the attacker to bypass configured ACL rules.

Severity
Medium
CVSS
5.8 (3.1)
Published
2024-10-23
CISA KEV
Not currently listed
Ecosystem
operating-system
Weaknesses
CWE-290

Affected products

  • cisco / adaptive_security_appliance_software / 9.8.1
  • cisco / adaptive_security_appliance_software / 9.8.1.5
  • cisco / adaptive_security_appliance_software / 9.8.1.7
  • cisco / adaptive_security_appliance_software / 9.8.2
  • cisco / adaptive_security_appliance_software / 9.8.2.8
  • cisco / adaptive_security_appliance_software / 9.8.2.14

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

Matched remediation archetype

General vulnerability remediation

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

Check exposure

  • Confirm the affected component, deployment paths, reachable interfaces, and enabled features from inventories and configuration, without probing production destructively.
  • Compare the advisory's affected conditions with the repository lockfiles, build manifests, artifacts, and runtime inventory.
  • Identify data sensitivity, trust boundaries, and privilege level for every confirmed affected deployment.

Remediate safely

  • Apply a vendor-supported fix or remove the affected component or feature; record the selected change and its source in the repository.
  • Update direct and transitive dependency locks, generated artifacts, deployment manifests, and asset inventories together.
  • Add a regression test for the documented unsafe condition using inert inputs and preserve rollback instructions.

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.