CVE-2023-20256
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 · uneditedMultiple 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.
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 confidenceLogic error in the per-user-override feature of Cisco ASA and FTD software causes interface ACLs to be bypassed. When the software constructs and applies per-user-override rules, it incorrectly allows traffic that should be denied to flow through the affected device, enabling unauthorized network access.
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= 9.8.4.22= 9.8.4.25= 9.8.4.26= 9.8.4.29= 9.8.4.32= 9.8.4.33= 9.8.4.34= 9.8.4.35= 9.8.4.39= 9.8.4.40= 9.8.4.41= 9.8.4.43= 6.2.3.16= 6.2.3.17= 6.2.3.18= 6.4.0.10= 6.4.0.11= 6.4.0.12= 6.4.0.13= 6.4.0.14= 6.4.0.15= 6.4.0.16= 6.6.1= 6.6.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify product and installed versionExecute 'show version' on the Cisco ASA or FTD device to obtain the exact software versionAffected if The installed version matches any of these: ASA 9.8.4.22, 9.8.4.25, 9.8.4.26, 9.8.4.29, 9.8.4.32, 9.8.4.33, 9.8.4.34, 9.8.4.35, 9.8.4.39, 9.8.4.40, 9.8.4.41, 9.8.4.43; FTD 6.2.3.16, 6.2.3.17, 6.2.3.18, 6.4.0.10, 6.4.0.11, 6.4.0.12, 6.4.0.13, 6.4.0.14, 6.4.0.15, 6.4.0.16, 6.6.1, 6.6.3
-
Confirm per-user-override feature is configuredRun 'show run all | include per-user-override' or review AAA/user authentication configuration to determine if per-user-override is enabledAffected if Per-user-override is enabled or configured on the device
-
Identify interfaces with per-user-override appliedReview the configuration with 'show run' and look for 'per-user-override' under interface configurations or AAA authorization settingsAffected if Any interface has per-user-override applied in the configuration
Device is affected if it runs an affected ASA or FTD version AND has per-user-override configured on any interface, allowing traffic that interface ACLs should deny.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedReview and correct per-user-override configuration on affected ASA/FTD devices; apply Cisco security updates if available; if per-user-override is not required, disable the feature.
Cisco ASA 9.8.4.31+ or 9.9.1+ / Cisco FTD 6.2.3.19+ or 6.4.0.11+ or 6.6.0+
- 1. Identify the current version of Cisco Adaptive Security Appliance (ASA) Software or Secure Firewall Threat Defense (FTD) Software by running 'show version' command
- 2. For ASA Software: Upgrade to version 9.8.4.31 or later, or upgrade to version 9.9.1 or later, or upgrade to version 9.10.1 or later
- 3. For FTD Software: If running 6.2.3.x, upgrade to version 6.2.3.19 or later
- 4. For FTD Software: If running 6.4.0.x, upgrade to version 6.4.0.11 or later
- 5. For FTD Software: Alternatively, upgrade to version 6.6.0 or later
- 6. After upgrade, verify the per-user-override feature configuration and test that ACLs are being applied correctly
- 7. Review all interface ACLs to ensure traffic filtering is functioning as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-20256 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-20256 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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