dbcve.org
Adaptive Security Appliance SoftwareOperating system · Cisco

CVE-2013-5512

HIGH · 7.1 CVSS v2.0 Published 2013-10-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Race condition in the HTTP Deep Packet Inspection (DPI) feature in Cisco Adaptive Security Appliance (ASA) Software 8.2.x before 8.2(5.46), 8.3.x before 8.3(2.39), 8.4.x before 8.4(5.5), 8.5.x before 8.5(1.18), 8.6.x before 8.6(1.12), 8.7.x before 8.7(1.4), 9.0.x before 9.0(1.4), and 9.1.x before 9.1(1.2), in certain conditions involving the spoof-server option or ActiveX or Java response inspection, allows remote attackers to cause a denial of service (device reload) via a crafted HTTP response, aka Bug ID CSCud37992.

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

Race condition in Cisco ASA's HTTP Deep Packet Inspection (DPI) feature allows remote attackers to cause device reload via crafted HTTP responses when certain conditions are met, specifically involving the spoof-server option or ActiveX/Java response inspection. The vulnerability affects multiple ASA software branches (8.2.x through 9.1.x) before their respective patched versions.

MitigationUpgrade Cisco ASA Software to version 8.2(5.46), 8.3(2.39), 8.4(5.5), 8.5(1.18), 8.6(1.12), 8.7(1.4), 9.0(1.4), or 9.1(1.2) or later. If immediate upgrade is not feasible, consider disabling HTTP DPI inspection for affected traffic or implementing rate limiting as a temporary measure.

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
Affected:= 8.2= 8.2\(1\)= 8.2\(2\)= 8.2\(3\)= 8.2\(3.9\)= 8.2\(4\)= 8.2\(4.1\)= 8.2\(4.4\)= 8.2\(5\)= 8.2\(5.35\)= 8.2\(5.38\)= 8.3\(1\)

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

AV:N/AC:M/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 checks

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

  1. Determine the Cisco ASA software version
    Log into the ASA CLI and run the command: show version. Review the output for the installed software version number.
    Affected if The installed version matches or falls within the 8.2.x through 9.1.x range before the patched versions (8.2(5.46), 8.3(2.39), 8.4(5.5), 8.5(1.18), 8.6(1.12), 8.7(1.4), 9.0(1.4), or 9.1(1.2))
  2. Verify if HTTP Deep Packet Inspection is enabled
    Run the command: show run | include inspection http. Also run: show service-policy to list active inspection policies.
    Affected if HTTP inspection is globally enabled or applied via a service policy (any 'inspection http' configuration is present)
  3. Check for the spoof-server option in HTTP inspection configuration
    Run: show run | include spoof-server. If present, run the full inspection policy configuration to see if it applies to traffic.
    Affected if The spoof-server option is configured within an HTTP inspection policy map
  4. Check for ActiveX or Java response inspection
    Run: show run | include (match response|class-map) to find policy maps. Then inspect the policy-map configuration for 'match res' commands that check for ActiveX or Java in HTTP responses.
    Affected if An HTTP inspection policy includes inspection for ActiveX or Java objects in HTTP responses

The environment is affected if the ASA runs a vulnerable 8.2.x-9.1.x version AND HTTP DPI inspection is enabled with either the spoof-server option or ActiveX/Java response inspection configured.

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 version 8.2(5.46), 8.3(2.39), 8.4(5.5), 8.5(1.18), 8.6(1.12), 8.7(1.4), 9.0(1.4), or 9.1(1.2) or later. If immediate upgrade is not feasible, consider disabling HTTP DPI inspection for affected traffic or implementing rate limiting as a temporary measure.

Fix this in Adaptive Security Appliance Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-5512 — 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-2013-5512 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