dbcve.org
Adaptive Security Appliance SoftwareApplication · Cisco

CVE-2011-0379

HIGH · 7.9 CVSS v2.0 Published 2011-02-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Buffer overflow on Cisco Adaptive Security Appliances (ASA) 5500 series devices with software 1.6.x; Cisco TelePresence Multipoint Switch (CTMS) devices with software 1.0.x, 1.1.x, 1.5.x, and 1.6.x; Cisco TelePresence endpoint devices with software 1.2.x through 1.6.x; and Cisco TelePresence Manager 1.2.x, 1.3.x, 1.4.x, 1.5.x, and 1.6.2 allows remote attackers to execute arbitrary code via a crafted Cisco Discovery Protocol packet, aka Bug IDs CSCtd75769, CSCtd75766, CSCtd75754, and CSCtd75761.

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

Buffer overflow vulnerability in Cisco Discovery Protocol (CDP) implementation allows remote attackers to execute arbitrary code via crafted CDP packets. Affected products include ASA 5500 series (1.6.x), TelePresence Multipoint Switch (1.0.x-1.6.x), TelePresence endpoints (1.2.x-1.6.x), and TelePresence Manager (1.2.x-1.6.2). The vulnerability has a CVSS score of 7.9 (HIGH), indicating network-adjacent attack vector with complete impact to confidentiality, integrity, and availability.

MitigationApply vendor patches for the specific bug IDs (CSCtd75769, CSCtd75766, CSCtd75754, CSCtd75761). If patches are unavailable, consider disabling Cisco Discovery Protocol on untrusted network segments or implementing network access controls to limit CDP packet exposure.

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 SoftwareApplication
Affected:= 1.6.0
5500 Series Adaptive Security ApplianceHardware / appliance
Affected:all versions
Asa 5500Hardware / appliance
Affected:all versions
Telepresence Multipoint Switch SoftwareApplication
Affected:= 1.0.4.0= 1.1.0= 1.1.1= 1.1.2= 1.5.0= 1.5.1= 1.5.2= 1.5.3= 1.5.4= 1.5.5= 1.5.6= 1.6.0
Telepresence Multipoint SwitchHardware / appliance
Affected:all versions
Telepresence System SoftwareApplication
Affected:= 1.2.3= 1.3.2= 1.4.7= 1.5.1= 1.5.3= 1.5.10= 1.5.11= 1.5.12= 1.5.13= 1.6.0= 1.6.2= 1.6.3
Telepresence System 1000Hardware / appliance
Affected:all versions
Telepresence System 1100Hardware / 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
Adjacent
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:A/AC:M/Au:N/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 device model and software version
    Run 'show version' or 'show inventory' on the device CLI to retrieve the exact model number and software version
    Affected if The model matches ASA 5500 series, TelePresence Multipoint Switch, TelePresence System 1000/1100, or TelePresence endpoints, and the version falls within 1.0.x-1.6.x for TelePresence or 1.6.x for ASA
  2. Confirm CDP is enabled on the device
    Run 'show cdp' or 'show cdp neighbor' to check if Cisco Discovery Protocol is active
    Affected if CDP is running (the vulnerability requires receiving crafted CDP packets, so CDP must be enabled)
  3. Verify the specific software version against affected releases
    Compare the installed version number to the affected version list: ASA = 1.6.0 or all versions; TelePresence Multipoint Switch = 1.0.4.0, 1.1.x series, 1.5.x series, 1.6.0; TelePresence System = 1.2.3, 1.3.2, 1.4.7, 1.5.x series, 1.6.0, 1.6.2, 1.6.3
    Affected if The exact version matches one listed in the affected versions or is an 'all versions' product in the 1.0.x-1.6.x range

A user is affected if they run an ASA 5500 series (any version or 1.6.x), TelePresence Multipoint Switch, TelePresence System (1000/1100 or listed versions), or TelePresence endpoint with CDP enabled, and the software version matches the specific versions in the affected list.

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

Apply vendor patches for the specific bug IDs (CSCtd75769, CSCtd75766, CSCtd75754, CSCtd75761). If patches are unavailable, consider disabling Cisco Discovery Protocol on untrusted network segments or implementing network access controls to limit CDP packet exposure.

Fix this in Adaptive Security Appliance Software Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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