dbcve.org
Adaptive Security Appliance SoftwareOperating system · Cisco

CVE-2010-4675

HIGH · 9.0 CVSS v2.0 Published 2011-01-07
Fix available
A fix is available. Upgrade to after 8.2 or later.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable 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.2(3) do not properly determine the interfaces for which TELNET connections should be permitted, which allows remote authenticated users to bypass intended access restrictions via vectors involving the "lowest security level interface," aka Bug ID CSCsv40504.

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.2(3) contain a flaw in the interface-based TELNET access control logic. The device incorrectly determines which interfaces permit TELNET connections, specifically failing to properly restrict access on the interface with the lowest security level. This allows authenticated remote users to bypass configured TELNET access restrictions and connect to interfaces they should not have access to.

MitigationUpgrade Cisco ASA software to version 8.2(3) or later to patch the interface selection logic flaw. As a compensating control, disable TELNET entirely on all interfaces and use SSH with properly configured access-lists.

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\(2\)= 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
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:S/C:C/I:C/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. Identify the ASA software version
    Log into the ASA CLI and run the command: show version. Look for the version number in the output (for example: 8.2(1), 8.2(2), 7.0(4), etc.)
    Affected if The version is 8.2(2) or lower, or matches one of these: 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, or 7.0.4. Compare your version to the affected ranges listed in the CVE.
  2. Determine if TELNET is enabled on any interface
    Run the command: show running-config | include telnet. This displays all TELNET configuration lines.
    Affected if Any output is returned showing TELNET is configured on one or more interfaces.
  3. List all interface security levels
    Run the command: show interface ip brief or show running-config interface. Look for the 'security-level' setting on each interface.
    Affected if Multiple interfaces exist with different security levels, and at least one interface has TELNET access configured.
  4. Verify the lowest security level interface TELNET access
    Run the command: show running-config | begin telnet to see which interfaces permit TELNET. Cross-reference with the interface security levels from the previous check.
    Affected if TELNET is allowed on an interface that is NOT the highest security interface, particularly on the interface with the lowest security level.

You are affected if your ASA runs software version 8.2(2) or earlier (or a 7.0.x variant listed in the CVE) AND TELNET is enabled on any interface, especially when multiple interfaces with different security levels exist.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 8.2
Interim mitigation

Upgrade Cisco ASA software to version 8.2(3) or later to patch the interface selection logic flaw. As a compensating control, disable TELNET entirely on all interfaces and use SSH with properly configured access-lists.

Recommended fix High confidence

Cisco ASA 8.2(3) or later

  1. 1. Verify current ASA software version by running 'show version' command
  2. 2. Backup current ASA configuration using 'write memory' or 'copy startup-config tftp://<server>'
  3. 3. Download Cisco ASA 8.2(3) or later from Cisco's official download site (cisco.com)
  4. 4. Upload the new software image to the ASA using 'copy tftp://<server>/<image> flash:'
  5. 5. Set the new boot image: 'boot system flash:<new-image-name>'
  6. 6. Reload the ASA: 'reload'
  7. 7. After reboot, verify the new version is running: 'show version'
  8. 8. Confirm the fix by checking that the telnet command properly respects interface security levels
Caveat Review Cisco ASA 8.2(3) release notes for any configuration changes or commands that may behave differently; always test in a non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Adaptive Security Appliance Software Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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