dbcve.org
Asa 5500Hardware / appliance · Cisco

CVE-2010-0567

MEDIUM · 5.0 CVSS v2.0 Published 2010-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Unspecified vulnerability in Cisco ASA 5500 Series Adaptive Security Appliance 7.0 before 7.0(8.10), 7.2 before 7.2(4.45), 8.0 before 8.0(5.1), 8.1 before 8.1(2.37), and 8.2 before 8.2(1.15); and Cisco PIX 500 Series Security Appliance; allows remote attackers to cause a denial of service (active IPsec tunnel loss and prevention of new tunnels) via a malformed IKE message through an existing tunnel to UDP port 4500, aka Bug ID CSCtc47782.

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 confidence

Denial of service vulnerability in Cisco ASA 5500 and PIX 500 security appliances allows remote attackers to send malformed IKE messages through existing IPsec tunnels to UDP port 4500, causing active tunnel loss and preventing new tunnel establishment. The vulnerability exists in IKE message processing within the affected software versions.

MitigationUpgrade Cisco ASA software to versions 7.0(8.10), 7.2(4.45), 8.0(5.1), 8.1(2.37), or 8.2(1.15) and later. For PIX devices, apply the appropriate patched version per the Cisco advisory.

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
Affected:= 7.1= 7.2= 8.0= 8.1= 8.2
Pix 500Hardware / appliance
Affected:all versions

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
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Run 'show version' or 'show inventory' to confirm the device is a Cisco ASA 5500 series or PIX 500 series security appliance
    Affected if Device model is Cisco ASA 5500 or PIX 500
  2. Check ASA software version
    Run 'show version' and locate the software version string (e.g., 7.1, 7.2, 8.0, 8.1, 8.2). Compare your version against the affected list: 7.1, 7.2, 8.0, 8.1, 8.2
    Affected if ASA version is 7.1, 7.2, 8.0, 8.1, or 8.2 (any release within these branches)
  3. Check PIX software version
    Run 'show version' on PIX devices to obtain the software version
    Affected if PIX device runs any software version (all versions affected)
  4. Verify IPsec VPN NAT-T is enabled
    Run 'show run | include nat-t' or 'show vpn-sessiondb' to check if NAT-T (UDP port 4500) IPsec VPN is configured and active
    Affected if IPsec VPN with NAT-T is enabled and tunnels exist on UDP port 4500

The environment is affected if the device is a Cisco ASA 5500 running version 7.1, 7.2, 8.0, 8.1, or 8.2, or any PIX 500 model, and IPsec VPN with NAT-T (UDP 4500) is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Cisco ASA software to versions 7.0(8.10), 7.2(4.45), 8.0(5.1), 8.1(2.37), or 8.2(1.15) and later. For PIX devices, apply the appropriate patched version per the Cisco advisory.

Fix this in Asa 5500 Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-0567 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-0567 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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