Intrusion Prevention SystemApplication · Cisco
CVE-2013-3411
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 IDSM-2 drivers in Cisco Intrusion Prevention System (IPS) Software on Cisco Catalyst 6500 devices with an IDSM-2 module allow remote attackers to cause a denial of service (device hang) via malformed IPv4 TCP packets, aka Bug ID CSCuh27460.
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 · moderate confidenceThe IDSM-2 drivers in Cisco Intrusion Prevention System (IPS) Software running on Cisco Catalyst 6500 switches with an IDSM-2 module contain a vulnerability where processing malformed IPv4 TCP packets can cause the device to hang, resulting in a denial of service. The vulnerability is remotely exploitable via network packets sent to the IDSM-2 module.
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
Intrusion Prevention SystemApplication
all versions
Idsm 2Hardware / appliance
all versionsCVSS 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.
-
Identify the hardware platformRun 'show version' or check the switch inventory to confirm the device is a Cisco Catalyst 6500 series switchAffected if The device is a Catalyst 6500 series switch with an IDSM-2 module installed and IPS software running on it
-
Verify IDSM-2 module presenceExecute 'show module' or 'show hardware' command on the Catalyst 6500 to list installed modules and identify if an IDSM-2 module is physically present in any slotAffected if An IDSM-2 module is installed in any slot of the Catalyst 6500 switch
-
Confirm IPS software is active on IDSM-2Run 'show ips module status' or 'show idsm2 status' if available, to verify that Cisco IPS Software is running on the IDSM-2 moduleAffected if The IDSM-2 module has Cisco IPS Software actively loaded and running on it
-
Check IDSM-2 traffic processing statusUse 'show ips interface' or similar command to confirm the IDSM-2 is actively processing inline traffic and monitoring IPv4 TCP packetsAffected if The IDSM-2 module is configured in inline mode and actively inspecting IPv4 TCP traffic
If you have a Cisco Catalyst 6500 switch with an IDSM-2 module running Cisco IPS Software, you are affected by this vulnerability because all versions of the IDSM-2 drivers contain the flaw that can be triggered by malformed IPv4 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 dataApply the appropriate Cisco IPS Software update or patch for the IDSM-2 module as specified in Cisco's advisory for Bug ID CSCuh27460. If immediate patching is not possible, consider network segmentation to limit exposure of the affected IDSM-2 module to untrusted networks.
Fix this in Intrusion Prevention System
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3411 — 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-2013-3411 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