CVE-2021-34792
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 memory management of Cisco Adaptive Security Appliance (ASA) Software and Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. This vulnerability is due to improper resource management when connection rates are high. An attacker could exploit this vulnerability by opening a significant number of connections on an affected device. A successful exploit could allow the attacker to cause the device to reload, resulting in a DoS condition.
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 confidenceMemory management vulnerability in Cisco ASA and FTD software where improper resource management during high connection rates allows an unauthenticated remote attacker to cause device reload, resulting in denial of service.
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>= 6.4.0, < 6.4.0.13>= 6.6.0, < 6.6.5>= 6.7.0, < 6.7.0.3>= 7.0.0, < 7.0.1>= 9.8.0, < 9.8.4.40>= 9.12.0, < 9.12.4.29>= 9.14.0, < 9.14.3.9>= 9.15.0, < 9.15.1.17>= 9.16.0, < 9.16.2.3= 009.014\(001.150\)= 099.017\(001.211\)= 099.017\(001.220\)= 099.017\(015.050\)= 009.014\(001.150\)= 099.017\(001.211\)= 099.017\(001.220\)= 099.017\(015.050\)= 009.014\(001.150\)= 099.017\(001.211\)= 099.017\(001.220\)= 099.017\(015.050\)= 009.014\(001.150\)= 099.017\(001.211\)= 099.017\(001.220\)= 099.017\(015.050\)= 009.014\(001.150\)= 099.017\(001.211\)= 099.017\(001.220\)= 099.017\(015.050\)= 009.014\(001.150\)= 099.017\(001.211\)= 099.017\(001.220\)= 099.017\(015.050\)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
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/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.
-
Confirm device is Cisco ASA or FTDIdentify the device type via show version or inventory - look for 'Cisco Adaptive Security Appliance' or 'Firepower Threat Defense' in the outputAffected if Device is not a Cisco ASA or FTD appliance (other Cisco devices are not affected by this CVE)
-
Obtain the software versionRun 'show version' on the ASA CLI or use 'show version' in FTD CLI. Look for the 'Cisco Adaptive Security Appliance Software' or 'Firepower Threat Defense' version numberAffected if Unable to retrieve version information from the device
-
Compare ASA version against affected rangesMatch the obtained ASA version number to these vulnerable ranges: 9.8.0 through 9.8.4.39, 9.12.0 through 9.12.4.28, 9.14.0 through 9.14.3.8, 9.15.0 through 9.15.1.16, 9.16.0 through 9.16.2.2Affected if ASA version falls within any of these ranges
-
Compare FTD version against affected rangesMatch the obtained FTD version number to these vulnerable ranges: 6.4.0 through 6.4.0.12, 6.6.0 through 6.6.4, 6.7.0 through 6.7.0.2, 7.0.0 through 7.0.0Affected if FTD version falls within any of these ranges
-
Check ASA firmware for specific affected versionsFor ASA 5505, 5512X, 5515X, 5525X, 5545X, 5555X - run 'show version' and look for firmware build numbers: 009.014(001.150), 099.017(001.211), 099.017(001.220), or 099.017(015.050)Affected if ASA firmware build matches any of these four specific versions
Your device is affected if it is a Cisco ASA or FTD appliance running a software or firmware version that falls within the listed vulnerable ranges, as the vulnerability triggers during high connection rates and can cause device reload.
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 · scoped6.4.0.136.6.56.7.0.3
Apply the vendor-supplied security update/patch for Cisco ASA and FTD software to remediate this vulnerability.
Firepower Threat Defense: upgrade to 6.4.0.13, 6.6.5, or 7.0.1 (depending on your current release train). ASA Software: upgrade to 9.8.4.40, 9.12.4.29, 9.14.3.9, or 9.15.1.17
- 1. Identify the currently installed Cisco ASA Software or FTD version by running the 'show version' command on the device
- 2. Determine which upgrade path applies based on your current version from the affected versions list
- 3. Access Cisco's software download page (tools.cisco.com) and download the appropriate fixed version for your device model
- 4. Transfer the software image to the device using FTP, SCP, or through the management interface
- 5. Install the new software image using the 'install' command or through the ASDM/FTD management interface
- 6. After installation, reload the device using the 'reload' command to complete the upgrade
- 7. Verify the upgrade was successful by running 'show version' and confirm the new version is installed
- 8. Verify normal device operation and that the vulnerability is mitigated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34792 — 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-2021-34792 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