Adaptive Security Appliance SoftwareOperating system · Cisco
CVE-2010-4682
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 · uneditedMemory leak on Cisco Adaptive Security Appliances (ASA) 5500 series devices with software before 8.2(3) allows remote attackers to cause a denial of service (memory consumption) by making multiple incorrect LDAP authentication attempts, aka Bug ID CSCtf29867.
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 leak vulnerability in Cisco ASA 5500 series devices running software versions prior to 8.2(3). Remote attackers can cause denial of service by making multiple failed LDAP authentication attempts, which progressively exhaust available memory until the device becomes unresponsive.
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
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:N/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 device modelUse the 'show version' command or check the physical device label to confirm it is a Cisco ASA 5500 Series Adaptive Security ApplianceAffected if The device is not an ASA 5500 series model, then this specific CVE does not apply
-
Check the installed software versionExecute 'show version' on the ASA CLI and locate the software version number in the outputAffected if The version is 8.2(2) or lower, 7.0.x series, or any version prior to 8.2(3)
-
Verify LDAP authentication is configuredRun 'show run | include ldap' or examine the AAA configuration with 'show run aaa' to see if LDAP authentication is enabled for management or network accessAffected if LDAP authentication is not configured, the memory leak trigger condition is not present
-
Check current memory utilizationUse the 'show memory' command to display current memory usage and compare to baseline or note if available memory is critically lowAffected if Memory is severely depleted after multiple failed LDAP authentication attempts, indicating active exploitation
The device is affected if it is a Cisco ASA 5500 series running software version 8.2(2) or lower (including 7.0.x versions) with LDAP authentication enabled, as the memory leak only triggers under those specific conditions.
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 resolve the memory leak. Consider implementing rate-limiting on LDAP authentication attempts or restricting management access to trusted networks as additional hardening measures.
Fix this in Adaptive Security Appliance Software
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-4682 — 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-4682 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