Asa 5500Hardware / appliance · Cisco
CVE-2010-0565
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 in Cisco ASA 5500 Series Adaptive Security Appliance 7.2 before 7.2(4.45), 8.0 before 8.0(4.44), 8.1 before 8.1(2.35), and 8.2 before 8.2(1.10), allows remote attackers to cause a denial of service (page fault and device reload) via a malformed DTLS message, aka Bug ID CSCtb64913 and "WebVPN DTLS Denial of Service Vulnerability."
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 exists in Cisco ASA 5500 Series Adaptive Security Appliances running affected versions of the firmware. Remote attackers can send malformed DTLS (Datagram Transport Layer Security) packets, specifically through the WebVPN feature, causing a page fault that leads to device reload.
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
Asa 5500Hardware / appliance
= 7.1= 7.2= 8.0= 8.1= 8.2
Pix 500Hardware / 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 device model and hardwareLog into the device and run 'show version' or check the device model via 'show hardware'. Confirm it is a Cisco ASA 5500 Series or Cisco PIX 500 Series appliance.Affected if Device is a Cisco ASA 5500 series or Cisco PIX 500 series appliance.
-
Check installed software versionRun 'show version' and locate the software version number in the output. Compare this version against the affected versions: 7.1, 7.2, 8.0, 8.1, or 8.2 for ASA; any version for PIX 500.Affected if Software version is 7.1, 7.2, 8.0, 8.1, or 8.2 on ASA 5500, or any version on PIX 500.
-
Verify WebVPN is enabledRun 'show run webvpn' or 'show vpn-sessiondb webvpn' to check if WebVPN is currently configured and active on the device.Affected if WebVPN is enabled and running on the device.
-
Check DTLS configuration under WebVPNRun 'show run webvpn' and look for 'dtls' or 'ssl dtls' configuration lines within the WebVPN context. Also check 'show run all webvpn' for full DTLS settings.Affected if DTLS is configured or enabled within the WebVPN settings.
The device is affected if it is an ASA 5500 series (versions 7.2, 8.0, 8.1, 8.2) or PIX 500 (any version) with WebVPN and DTLS enabled, allowing malformed DTLS packets to trigger a 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.
From vendor dataUpgrade Cisco ASA to version 7.2(4.45), 8.0(4.44), 8.1(2.35), 8.2(1.10) or later to patch the vulnerability. If immediate upgrade is not possible, consider disabling WebVPN or implementing network-level filtering to limit DTLS traffic sources.
Fix this in Asa 5500
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-0565 — 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-0565 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