CVE-2016-6431
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 · uneditedA vulnerability in the local Certificate Authority (CA) feature of Cisco ASA Software before 9.6(1.5) could allow an unauthenticated, remote attacker to cause a reload of the affected system. The vulnerability is due to improper handling of crafted packets during the enrollment operation. An attacker could exploit this vulnerability by sending a crafted enrollment request to the affected system. An exploit could allow the attacker to cause the reload of the affected system. Note: Only HTTPS packets directed to the Cisco ASA interface, where the local CA is allowing user enrollment, can be used to trigger this vulnerability. This vulnerability affects systems configured in routed firewall mode and in single or multiple context mode.
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 confidenceA denial-of-service vulnerability in Cisco ASA Software's local Certificate Authority feature allows unauthenticated remote attackers to cause system reload by sending crafted HTTPS enrollment packets. The vulnerability stems from improper handling of these packets during the enrollment operation and affects systems in routed firewall mode with single or multiple context configurations running versions prior to 9.6(1.5).
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= 8.0.2.11= 8.0.2.15= 8.0.3= 8.0.3.6= 8.0.3.12= 8.0.3.19= 8.0.4= 8.0.4.3= 8.0.4.9= 8.0.4.16= 8.0.4.23= 8.0.4.25CVSS 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
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 Cisco ASA device and versionRun 'show version' on the ASA CLI or check through ASDM to retrieve the installed software versionAffected if The device is running Cisco ASA Software version 8.0.2.11, 8.0.2.15, 8.0.3, 8.0.3.6, 8.0.3.12, 8.0.3.19, 8.0.4, 8.0.4.3, 8.0.4.9, 8.0.4.16, 8.0.4.23, 8.0.4.25, or any version prior to 9.6(1.5)
-
Verify local CA feature is enabledRun 'show run all crypto ca' or 'show crypto ca server' to check if the local Certificate Authority is configured and runningAffected if The local CA (crypto ca server) feature is enabled and configured on the device
-
Confirm firewall mode is routedRun 'show firewall' or check the mode via 'show run all global | include mode' to determine the operational modeAffected if The ASA is operating in routed firewall mode (not transparent mode)
-
Check context configurationRun 'show mode' or 'show context' to see if the device is in single or multiple context modeAffected if The device is running in any context mode (single or multiple) with routed firewall mode
The environment is affected if the Cisco ASA is running an affected version (8.0.x versions listed or any version prior to 9.6(1.5)) with the local CA feature enabled in routed firewall mode.
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.
From vendor dataUpgrade Cisco ASA Software to version 9.6(1.5) or later. If immediate upgrading is not feasible, disable the local CA feature or restrict access to the enrollment interface to mitigate the risk.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6431 — 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-2016-6431 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