CVE-2012-0335
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 · uneditedCisco Adaptive Security Appliances (ASA) 5500 series devices with software 7.2 through 8.4 do not properly perform proxy authentication during attempts to cut through a firewall, which allows remote attackers to obtain sensitive information via a connection attempt, aka Bug ID CSCtx42746.
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 · moderate confidenceThe vulnerability exists in Cisco ASA 5500 series devices running software versions 7.2 through 8.4, where proxy authentication is not properly enforced when attempting to cut through the firewall. This allows unauthenticated remote attackers to potentially obtain sensitive information through connection attempts without proper proxy authentication validation.
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= 7.2= 7.2\(1\)= 7.2\(1.22\)= 7.2\(2\)= 7.2\(2.5\)= 7.2\(2.7\)= 7.2\(2.8\)= 7.2\(2.10\)= 7.2\(2.14\)= 7.2\(2.15\)= 7.2\(2.16\)= 7.2\(2.17\)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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 Cisco ASA device modelRun 'show version' or 'show hardware' command on the ASA CLI to confirm the device is an ASA 5500 series modelAffected if The device is any ASA 5500 series model (ASA 5505, 5510, 5520, 5540, 5550)
-
Check the installed software versionRun 'show version' on the ASA CLI and locate the 'Software Version' line. Compare this version number against the affected range of 7.2 through 8.4Affected if The software version is 7.2.x, 8.0.x, 8.1.x, 8.2.x, 8.3.x, or 8.4.x (any version from 7.2 through 8.4 inclusive)
-
Verify proxy authentication feature configurationRun 'show running-config' and search for 'proxy' or 'authentication' related commands such as 'aaa authentication proxy', 'aaa-server', or authentication policy configurationsAffected if Proxy authentication is configured on the ASA (the vulnerability applies when proxy authentication is meant to be enforced but is not properly validated)
-
Inspect cut-through proxy configurationRun 'show running-config | include cut-through' or check for 'cut-through-proxy' in the configuration. Also check the authentication server configuration with 'show aaa-server'Affected if Cut-through proxy feature is enabled and the authentication server is configured but validation is bypassed
A user is affected if they have a Cisco ASA 5500 series device running software versions 7.2 through 8.4 with proxy authentication configured that can be bypassed by unauthenticated connection attempts.
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 a version beyond 8.4 that addresses this vulnerability, or implement additional authentication controls on proxy connections to mitigate the issue until patching is possible.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0335 — 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-2012-0335 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