iOSOperating system · Cisco
CVE-2011-0350
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 · uneditedUnspecified vulnerability in Cisco IOS 12.4(24)MD before 12.4(24)MD2 on the Cisco Content Services Gateway Second Generation (aka CSG2) allows remote attackers to cause a denial of service (device hang or reload) via crafted TCP packets, aka Bug ID CSCth41891, a different vulnerability than CVE-2011-0349.
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 confidenceA vulnerability in Cisco IOS 12.4(24)MD on the Cisco Content Services Gateway Second Generation (CSG2) allows remote attackers to send crafted TCP packets that cause the device to hang or reload, resulting in denial of service.
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
= 12.4\(24\)md= 12.4\(24\)md1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device is a Cisco CSG2Identify the hardware model using 'show version' or 'show inventory' command. Look for 'Content Services Gateway Second Generation' or 'CSG2' in the output.Affected if The device model is Cisco CSG2 (Content Services Gateway Second Generation)
-
Check Cisco IOS versionExecute 'show version' on the device console or via SSH. Locate the line displaying the IOS version, typically formatted as 'Version 12.4(24)MD' or similar.Affected if The IOS version displayed is exactly 12.4(24)md or 12.4(24)md1
-
Verify the MD train designationIn the 'show version' output, confirm the train identifier includes 'MD' (Maintenance Desktop) after the 12.4(24) version number. The full version string should appear as 12.4(24)MD, 12.4(24)MD1, or similar.Affected if The version train is 12.4(24)MD (or MD1) specifically, not another 12.4 subversion train
-
Confirm no later patch appliedCompare your installed version against the affected range. Versions prior to 12.4(24)MD2 remain vulnerable. If your version shows MD2 or higher (e.g., 12.4(24)MD2, 12.4(24)MD3), the issue is patched.Affected if The installed version is 12.4(24)MD or 12.4(24)MD1 with no subsequent patch applied
The environment is affected if the device is a Cisco CSG2 running Cisco IOS version 12.4(24)MD or 12.4(24)MD1, as these versions contain the vulnerability to denial of service from crafted TCP packets.
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 IOS on CSG2 devices to version 12.4(24)MD2 or later to patch the vulnerability.
Fix this in iOS
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing2.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,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0350 — 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-2011-0350 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