dbcve.org
Adaptive Security Appliance SoftwareOperating system · Cisco

CVE-2024-20293

MEDIUM · 5.8 CVSS v3.1 Published 2024-05-22
Fix available
A fix is available. Upgrade to after 9.19.1.24 or later.
See remediation →
67/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability in the activation of an access control list (ACL) on Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to bypass the protection that is offered by a configured ACL on an affected device. This vulnerability is due to a logic error that occurs when an ACL changes from inactive to active in the running configuration of an affected device. An attacker could exploit this vulnerability by sending traffic through the affected device that should be denied by the configured ACL. The reverse condition is also true—traffic that should be permitted could be denied by the configured ACL. A successful exploit could allow the attacker to bypass configured ACL protections on the affected device, allowing the attacker to access trusted networks that the device might be protecting. Note: This vulnerability applies to both IPv4 and IPv6 traffic as well as dual-stack ACL configurations in which both IPv4 and IPv6 ACLs are configured on an interface.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A logic error in Cisco ASA and FTD software allows ACLs to be bypassed when they transition from inactive to active state in the running configuration. An unauthenticated remote attacker can send traffic through the device that should be denied by the configured ACL, or conversely have traffic that should be permitted be denied. This affects IPv4, IPv6, and dual-stack ACL configurations.

MitigationApply the vendor patch when available. In the interim, verify ACL configurations are functioning as intended and monitor for unexpected traffic patterns that may indicate bypass attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Adaptive Security Appliance SoftwareOperating system
Affected:>= 9.19.1, <= 9.19.1.24= 9.20.1= 9.20.1.5
Secure Firewall Threat DefenseApplication
Affected:>= 7.3.0, <= 7.4.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the ASA software version
    Run 'show version' or 'show running-config | include version' to display the installed ASA software version
    Affected if The version falls within >= 9.19.1 through <= 9.19.1.24, equals 9.20.1, or equals 9.20.1.5
  2. Identify the FTD software version
    Run 'show version' on the FTD device or check via FMC to determine the FTD version
    Affected if The version falls within >= 7.3.0 through <= 7.4.0
  3. Verify ACL configuration exists
    Run 'show access-list' to list all configured ACLs on the device
    Affected if IPv4, IPv6, or dual-stack ACLs are configured on the device and the software version is vulnerable
  4. Check for recent ACL modifications
    Run 'show access-list [acl_name] hitcount' or review configuration change logs for recent ACL activations or modifications
    Affected if ACLs have recently been added, modified, or activated in the running configuration on a vulnerable device
  5. Test ACL enforcement behavior
    Send test traffic intended to be denied by specific ACL rules and verify it is blocked; alternatively, send traffic intended to be permitted and verify it is allowed
    Affected if Traffic behavior does not match the configured ACL rules (traffic passes when it should be denied, or is blocked when it should be allowed)

A user is affected if their device runs a vulnerable ASA (9.19.1.x, 9.20.1, or 9.20.1.5) or FTD (7.3.x through 7.4.x) version and has IPv4, IPv6, or dual-stack ACLs configured that have recently transitioned from inactive to active state.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 9.19.1.24
Interim mitigation

Apply the vendor patch when available. In the interim, verify ACL configurations are functioning as intended and monitor for unexpected traffic patterns that may indicate bypass attempts.

Fix this in Adaptive Security Appliance Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-20293 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-20293 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data