dbcve.org
Adaptive Security Appliance SoftwareOperating system · Cisco

CVE-2024-20384

MEDIUM · 5.8 CVSS v3.1 Published 2024-10-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Network Service Group (NSG) 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. This vulnerability is due to a logic error that occurs when NSG ACLs are populated on an affected device. An attacker could exploit this vulnerability by establishing a connection to the affected device. A successful exploit could allow the attacker to bypass configured ACL rules.

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 · moderate confidence

A logic error in the Network Service Group (NSG) feature causes configured access control lists to not be properly populated on Cisco ASA and FTD devices. This allows an unauthenticated remote attacker to establish a connection and bypass ACL rules that should deny traffic, permitting unauthorized flows through the affected device.

MitigationApply Cisco-provided patches when available; meanwhile, implement compensating controls such as additional filtering at downstream devices or alternative ACL implementations to enforce the intended deny rules.

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.16.1= 9.16.1.28= 9.16.2= 9.16.2.3= 9.16.2.7= 9.16.2.11= 9.16.2.13= 9.16.2.14= 9.16.3= 9.16.3.3= 9.16.3.14= 9.16.3.15
Secure Firewall Threat DefenseApplication
Affected:= 7.0.0= 7.0.0.1= 7.0.1= 7.0.1.1= 7.0.2= 7.0.2.1= 7.0.3= 7.0.4= 7.0.5= 7.0.6= 7.0.6.1= 7.0.6.2

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 device type and software version
    Run 'show version' on the ASA or FTD device CLI to obtain the software version
    Affected if The version matches any of the listed affected versions: ASA 9.16.1 through 9.16.3.15 or FTD 7.0.0 through 7.0.6.2
  2. Confirm Network Service Group feature is in use
    Run 'show run object network-service-group' or check configuration for 'network-service-group' objects
    Affected if NSG objects are defined in the device configuration
  3. Verify ACLs reference Network Service Groups
    Run 'show run access-list' and search for entries that reference network-service-group objects, or check ACL hits with 'show access-list'
    Affected if Any access-list entries use NSG objects for filtering traffic
  4. Inspect ACL compilation status
    Run 'show access-list' and check the compilation status or hit counts; also run 'show running-config | include access-list' to review ACL entries
    Affected if ACLs are configured but traffic may be passing that should be denied based on NSG references

The device is affected if it runs a matching ASA or FTD version AND uses Network Service Groups in access-list configurations, because the ACL population logic failure can allow traffic that should be denied to pass through.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Cisco-provided patches when available; meanwhile, implement compensating controls such as additional filtering at downstream devices or alternative ACL implementations to enforce the intended deny rules.

Fix this in Adaptive Security Appliance Software Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-20384 — 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-20384 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