dbcve.org
iOSOperating system · Cisco

CVE-2011-2064

HIGH · 7.8 CVSS v2.0 Published 2011-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 IOS 12.4MDA before 12.4(24)MDA5 on the Cisco Content Services Gateway - Second Generation (CSG2) allows remote attackers to cause a denial of service (device reload) via crafted ICMP packets, aka Bug ID CSCtl79577.

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

This is a denial of service vulnerability in Cisco IOS 12.4MDA on the Cisco Content Services Gateway Second Generation (CSG2). Remote attackers can send specially crafted ICMP packets that cause the device to reload, resulting in service disruption. The vulnerability exists in versions prior to 12.4(24)MDA5.

MitigationUpgrade Cisco IOS to version 12.4(24)MDA5 or later. As a workaround, filter or block untrusted ICMP traffic at network boundaries to prevent external attackers from reaching the affected device.

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
iOSOperating system
Affected:= 12.4\(24\)md1= 12.4\(24\)md2= 12.4\(24\)md3= 12.4\(24\)md4= 12.4\(24\)mda= 12.4mda
Content Services Gateway Second GenerationHardware / 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
None
Availability
Complete

AV:N/AC:L/Au:N/C:N/I:N/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
    Use the 'show version' command or check the device hardware label to confirm it is a Cisco Content Services Gateway Second Generation (CSG2)
    Affected if The device is a Cisco CSG2
  2. Check the IOS version
    Run 'show version' and look for the IOS version string. It should show 12.4MDA family such as 12.4(24)md1, 12.4(24)md2, 12.4(24)md3, 12.4(24)md4, 12.4(24)mda, or 12.4mda
    Affected if The IOS version is 12.4MDA and is prior to 12.4(24)MDA5
  3. Confirm the IOS train
    In the 'show version' output, verify the software image name contains 'mda' in the train designation
    Affected if The IOS image includes the 'mda' train
  4. Verify ICMP network exposure
    Check network configuration and ACLs to determine if the CSG2 device can receive ICMP packets from untrusted external networks
    Affected if The device is reachable by untrusted ICMP traffic from outside the trusted network

You are affected if your device is a Cisco CSG2 running Cisco IOS 12.4MDA versions prior to 12.4(24)MDA5 and the device is exposed to untrusted ICMP traffic.

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

Upgrade Cisco IOS to version 12.4(24)MDA5 or later. As a workaround, filter or block untrusted ICMP traffic at network boundaries to prevent external attackers from reaching the affected device.

Fix this in iOS Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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