Pix Security ApplianceHardware / appliance · Cisco
CVE-2008-2059
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 Appliance (ASA) and Cisco PIX security appliance 8.0.x before 8.0(3)9 allows remote attackers to bypass control-plane ACLs for the device via unknown vectors.
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 confidenceA vulnerability in Cisco ASA and PIX security appliances running software version 8.0.x before 8.0(3)9 allows remote attackers to bypass control-plane ACLs (Access Control Lists) via unknown vectors, potentially enabling unauthorized access to device management functions.
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
Pix Security ApplianceHardware / appliance
= 8.0
Adaptive Security Appliance SoftwareOperating system
= 8.0CVSS 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
- Complete
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:C/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 device model and software versionConnect to the device console or SSH and execute the 'show version' command. Look for the model line (Cisco ASA or Cisco PIX) and the software version number displayed in the output.Affected if The device is a Cisco ASA or PIX running software version 8.0.x that is earlier than 8.0(3)9 (for example, 8.0, 8.0(1), 8.0(2), 8.0(3), 8.0(3)1, etc.)
-
Verify control-plane ACL configurationExecute the 'show running-config access-list control-plane' or 'show access-list control-plane' command to display any ACLs applied to the control plane.Affected if Control-plane ACLs are configured and the device software version falls within the vulnerable 8.0.x range before 8.0(3)9
-
Confirm management access methodsReview the current configuration with 'show running-config | include http|ssh|telnet' to see which management interfaces (HTTP, SSH, telnet) are enabled and from which sources.Affected if Management access is enabled and reachable, combined with the vulnerable software version and control-plane ACLs in use
A Cisco ASA or PIX device is affected if it runs any software version 8.0.x prior to 8.0(3)9 and has control-plane ACLs configured to filter management access.
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/PIX devices to version 8.0(3)9 or later to remediate this control-plane ACL bypass vulnerability.
Fix this in Pix Security Appliance
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing3.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 $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-2059 — 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-2008-2059 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