dbcve.org
Adaptive Security Appliance SoftwareOperating system · Cisco

CVE-2010-4689

HIGH · 7.8 CVSS v2.0 Published 2011-01-07
Fix available
A fix is available. Upgrade to after 8.3 or later.
See remediation →
87/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
Cisco Adaptive Security Appliances (ASA) 5500 series devices with software before 8.3(2) do not properly preserve ACL behavior after a migration, which allows remote attackers to bypass intended access restrictions via an unspecified type of network traffic that had previously been denied, aka Bug ID CSCte46460.

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

Cisco ASA 5500 series devices running software versions before 8.3(2) fail to properly preserve Access Control List (ACL) behavior during or after a migration, causing previously denied network traffic to be permitted. This allows remote attackers to bypass intended security restrictions.

MitigationUpgrade Cisco ASA software to version 8.3(2) or later to resolve the ACL migration issue. After upgrade, audit all ACL configurations to verify deny rules are correctly applied.

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.3\(1\)= 7.0= 7.0\(0\)= 7.0\(2\)= 7.0\(4\)= 7.0\(5\)= 7.0\(5.2\)= 7.0\(6.7\)= 7.0.1= 7.0.1.4= 7.0.2= 7.0.4
5500 Series Adaptive Security ApplianceHardware / appliance
Affected:all versions
Asa 5500Hardware / 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
Complete
Availability
None

AV:N/AC:L/Au:N/C:N/I:C/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 checks

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

  1. Identify Cisco ASA device model
    Run 'show version' or 'show hardware' command on the ASA CLI to determine if the device is an ASA 5500 series appliance
    Affected if Device is a Cisco ASA 5500 Series Adaptive Security Appliance or ASA 5500 model
  2. Check installed software version
    Run 'show version' and locate the 'Software Version' line. Compare it against affected versions: 8.3(1) and below, or any 7.0.x version (7.0, 7.0(0), 7.0(2), 7.0(4), 7.0(5), 7.0(5.2), 7.0(6.7), 7.0.1, 7.0.1.4, 7.0.2, 7.0.4)
    Affected if Software version is 8.3(1) or lower, or matches any 7.0.x variant listed in the affected versions
  3. Determine if a software migration or upgrade occurred
    Review startup configuration and running configuration using 'show startup-config' and 'show running-config' for any signs of version changes, or check logs for upgrade/migration events
    Affected if The device underwent a software upgrade or migration, particularly from pre-8.3 to 8.3+ version
  4. Audit Access Control List deny rules
    Run 'show access-list' to view all ACL entries. Specifically examine any 'deny' rules that were intended to block traffic. Compare the configured deny entries against expected security policy
    Affected if Deny rules are present in ACLs but traffic that should be denied is being permitted, indicating ACLs were not properly migrated

The environment is affected if the device is a Cisco ASA 5500 series running software version 8.3(1) or below (or any 7.0.x variant) and has undergone a software migration, with observed permit anomalies in ACL deny rules.

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
Upgrade available Upgrade to a release after 8.3
Interim mitigation

Upgrade Cisco ASA software to version 8.3(2) or later to resolve the ACL migration issue. After upgrade, audit all ACL configurations to verify deny rules are correctly applied.

Fix this in Adaptive Security Appliance Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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