CVE-2020-3304
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 web interface of Cisco Adaptive Security Appliance (ASA) Software and Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to cause an affected device to reload unexpectedly, resulting in a denial of service (DoS) condition. The vulnerability is due to a lack of proper input validation of HTTP requests. An attacker could exploit this vulnerability by sending a crafted HTTP request to an affected device. An exploit could allow the attacker to cause a DoS condition. Note: This vulnerability applies to IP Version 4 (IPv4) and IP Version 6 (IPv6) HTTP traffic.
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 vulnerability in the web interface of Cisco ASA and FTD allows an unauthenticated remote attacker to send crafted HTTP requests that cause the device to reload unexpectedly, resulting in denial of service. The vulnerability stems from improper input validation of HTTP requests and affects both IPv4 and IPv6 traffic.
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.6.4.45< 6.3.0.6>= 6.4.0, < 6.4.0.10>= 6.5.0, < 6.5.0.5>= 6.6.0, < 6.6.1>= 9.8.0, < 9.8.4.22>= 9.9.0, < 9.9.2.80>= 9.10.0, < 9.10.1.44>= 9.12.0, < 9.12.3.12>= 9.13.0, < 9.13.1.12>= 9.14.0, < 9.14.1.10CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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.
-
Verify HTTP web interface is enabled on the deviceRun 'show running-config http' or 'show running-config | include http server' to see if the HTTP server is enabled. Also check with 'show http server' to confirm the web interface status.Affected if If HTTP server is enabled (the vulnerability requires the web interface to be accessible) - if HTTP is disabled, the device is not exploitable via this vector.
-
Identify the installed Cisco ASA software versionConnect to the ASA CLI and run 'show version' to display the running software version. Look for the version number displayed in the output.Affected if The version falls within one of these vulnerable ranges: < 9.6.4.45, >= 9.8.0 and < 9.8.4.22, >= 9.9.0 and < 9.9.2.80, >= 9.10.0 and < 9.10.1.44, >= 9.12.0 and < 9.12.3.12, >= 9.13.0 and < 9.13.1.12, >= 9.14.0 and < 9.14.1.10.
-
Identify the installed Cisco Firepower Threat Defense versionConnect to the FTD device and run 'show version' or access the management console to view the FTD software version.Affected if The version falls within one of these vulnerable ranges: < 6.3.0.6, >= 6.4.0 and < 6.4.0.10, >= 6.5.0 and < 6.5.0.5, >= 6.6.0 and < 6.6.1.
-
Confirm IPv4 or IPv6 HTTP access is permittedCheck the access list applied to the HTTP server with 'show running-config | include http' to see which interfaces and networks are permitted to access the web interface.Affected if The HTTP service is exposed to untrusted networks (such as outside interfaces or any interface accessible from the internet).
A device is affected if it runs a vulnerable Cisco ASA or FTD version AND has the HTTP web interface enabled and accessible - both conditions must be true for the device to be exploitable.
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 data6.3.0.66.4.0.106.5.0.5
Apply the vendor-supplied software update from Cisco to patch the input validation vulnerability. As a workaround, restrict or disable HTTP web interface access to untrusted networks until the patch can be deployed.
- 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-2020-3304 — 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-2020-3304 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