Adaptive Security Appliance SoftwareOperating system · Cisco
CVE-2010-4676
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 · uneditedUnspecified vulnerability on Cisco Adaptive Security Appliances (ASA) 5500 series devices with software before 8.2(3) allows remote authenticated users to cause a denial of service (device crash) via a high volume of IPsec traffic, aka Bug ID CSCsx52748.
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 confidenceThis vulnerability affects Cisco ASA 5500 series security appliances running software versions prior to 8.2(3). An authenticated remote attacker can trigger a denial of service condition by sending a high volume of IPsec traffic to the device, causing it to crash. The attack requires valid authentication credentials.
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
<= 8.2\(2\)= 7.0= 7.0\(0\)= 7.0\(2\)= 7.0\(4\)= 7.0\(5\)= 7.0\(5.2\)= 7.0\(6.7\)= 7.0.1= 7.0.1.4= 7.0.2= 7.0.4
5500 Series Adaptive Security ApplianceHardware / appliance
all versions
Asa 5500Hardware / appliance
all versionsCVSS 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
- Authentication
- Single
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:S/C:N/I:N/A:C
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 the ASA modelRun 'show version' or check the hardware model to confirm the device is a Cisco ASA 5500 series Adaptive Security ApplianceAffected if The device is a Cisco ASA 5500 Series or Cisco ASA 5500 model
-
Check the software versionRun 'show version' and locate the 'Software Version' line. Compare your installed version against the affected ranges: any version <= 8.2(2), or specifically 7.0, 7.0(0), 7.0(2), 7.0(4), 7.0(5), 7.0(5.2), 7.0(6.7), 7.0.1, 7.0.1.4, 7.0.2, or 7.0.4Affected if The software version is 8.2(2) or lower, or matches any of the specific 7.x versions listed
-
Verify IPsec is enabledRun 'show ipsec sa' or 'show crypto ipsec sa' to check if any IPsec security associations are active or if IPsec is configuredAffected if IPsec is configured or active on the device (the vulnerability is triggered via IPsec traffic)
-
Confirm authentication is configuredRun 'show running-config aaa' or 'show uauth' to verify that authentication methods are configured for IPsec or administrative accessAffected if Authentication is enabled (the attack requires valid credentials to trigger the DoS condition)
You are affected if you run a Cisco ASA 5500 series appliance with software version 8.2(2) or lower (or any of the specific 7.x versions listed), have IPsec enabled, and authentication is configured on the device.
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 8.2(3) or later to patch this vulnerability. Consider implementing rate limiting on IPsec traffic as an additional compensating control while planning the upgrade.
Fix this in Adaptive Security Appliance Software
Scoped from the published advisory
- Consultation6.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 $4,368.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-4676 — 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-2010-4676 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