CVE intelligence and bounded remediation

CVE-2023-20245 — Cisco Adaptive Security Appliance Software security vulnerability

Medium CVSS 5.8

Multiple vulnerabilities in the per-user-override feature of 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 be denied to flow through an affected device. These vulnerabilities are due to a logic error that could occur when the affected software constructs and applies per-user-override rules. An attacker could exploit these vulnerabilities by connecting to a network through an affected device that has a vulnerable configuration. A successful exploit could allow the attacker to bypass the interface ACL and access resources that would should be protected.

Severity
Medium
CVSS
5.8 (3.1)
Published
2023-11-01
CISA KEV
Not currently listed
Ecosystem
operating-system
Weaknesses
CWE-290

Affected products

  • cisco / adaptive_security_appliance_software / 9.8.3.14
  • cisco / adaptive_security_appliance_software / 9.8.3.16
  • cisco / adaptive_security_appliance_software / 9.8.3.18
  • cisco / adaptive_security_appliance_software / 9.8.3.21
  • cisco / adaptive_security_appliance_software / 9.8.3.26
  • cisco / adaptive_security_appliance_software / 9.8.3.29

Showing 6 representative product identities from 210 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.