iOSOperating system · Cisco
CVE-2012-0382
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 · uneditedThe Multicast Source Discovery Protocol (MSDP) implementation in Cisco IOS 12.0, 12.2 through 12.4, and 15.0 through 15.2 and IOS XE 2.1.x through 2.6.x and 3.1.xS through 3.4.xS before 3.4.1S and 3.1.xSG and 3.2.xSG before 3.2.2SG allows remote attackers to cause a denial of service (device reload) via encapsulated IGMP data in an MSDP packet, aka Bug ID CSCtr28857.
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 confidenceThe Multicast Source Discovery Protocol (MSDP) implementation in Cisco IOS and IOS XE contains a parsing vulnerability when processing encapsulated IGMP data within MSDP packets. A remote, unauthenticated attacker can send specially crafted MSDP packets containing encapsulated IGMP data, causing the affected device to 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.0= 12.2= 12.2\(1\)= 12.2\(1\)dx= 12.2\(1\)s= 12.2\(1\)t= 12.2\(1\)xa= 12.2\(1\)xd= 12.2\(1\)xd1= 12.2\(1\)xd3= 12.2\(1\)xd4= 12.2\(1\)xe
Ios XeOperating system
>= 2.1.0, <= 2.6.2>= 3.1.0s, < 3.4.1s>= 3.1.0sg, < 3.2.2sgCVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
-
Check Cisco IOS/IOS XE versionRun 'show version' and locate the version string (e.g., 'Version 12.2(1)T' or 'Version 15.1(4)M' for IOS, or check for IOS XE strings like 'Version 3.1.0S').Affected if The version falls within any of these ranges: 12.0 family, 12.2 family (including 12.2(1), 12.2(1)d*, 12.2(1)s*, 12.2(1)t*, 12.2(1)x* variants); IOS XE 2.1.0 to 2.6.2; IOS XE 3.1.0S to 3.4.0S; IOS XE 3.1.0SG to 3.2.1SG.
-
Verify if MSDP is enabledRun 'show ip msdp summary' or inspect the configuration with 'show running-config | include ip msdp' or 'show running-config | include msdp'.Affected if MSDP is enabled and configured with at least one MSDP peer.
-
Confirm device is an MSDP peerRun 'show ip msdp peer' to display MSDP peer status and verify active peer connections.Affected if The device has one or more MSDP peers configured and the peer state is active or up.
You are affected if your device runs a vulnerable IOS/IOS XE version AND has MSDP enabled with at least one configured peer, as the vulnerability is triggered by processing crafted MSDP packets containing encapsulated IGMP data.
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 data3.2.2sg3.4.1s
Apply the appropriate Cisco IOS or IOS XE software update (IOS XE 3.4.1S or later, 3.2.2SG or later for SG variants) after scheduling a maintenance window. If immediate patching is not possible, consider filtering MSDP traffic at network boundaries or disabling MSDP if not required.
Fix this in iOS
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing4.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0382 — 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-2012-0382 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