Intrusion Prevention SystemApplication · Cisco
CVE-2014-3402
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 authentication-manager process in the web framework in Cisco Intrusion Prevention System (IPS) 7.0(8)E4 and earlier in Cisco Intrusion Detection System (IDS) does not properly manage user tokens, which allows remote attackers to cause a denial of service (temporary MainApp hang) via a crafted connection request to the management interface, aka Bug ID CSCuq39550.
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 authentication-manager process in the web framework of Cisco IPS 7.0(8)E4 and earlier (and Cisco IDS) does not properly manage user tokens, allowing remote attackers to cause denial of service via crafted connection requests to the management interface, resulting in temporary MainApp hang.
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
<= 7.0\(8\)e4= 7.0= 7.0\(1\)e3= 7.0\(2\)e3= 7.0\(2\)e4= 7.0\(3\)e4= 7.0\(4\)e4= 7.0\(5a\)e4= 7.0\(6\)e4= 7.0\(7\)e4CVSS 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
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 Cisco IPS software versionAccess the Cisco IPS CLI and run the 'show version' command, or log into the IPS Device Manager web interface and check the version information in the System menuAffected if The displayed version matches any of the affected versions: 7.0(8)e4 or earlier, including 7.0, 7.0(1)e3, 7.0(2)e3, 7.0(2)e4, 7.0(3)e4, 7.0(4)e4, 7.0(5a)e4, 7.0(6)e4, or 7.0(7)e4
-
Confirm web management interface is enabledIn the CLI, run 'show http' or check the IPS Device Manager configuration to see if the web-based management interface is activeAffected if The HTTP or HTTPS management interface is enabled, exposing the authentication-manager process to network requests
-
Verify management interface accessibilityCheck network configuration via 'show interface' or the device access list to determine if the management interface is reachable from network segmentsAffected if The management interface is accessible from network locations, particularly untrusted segments, increasing exposure to remote attackers
You are affected if your Cisco IPS version is 7.0(8)e4 or earlier and the web-based management interface is enabled and reachable on your network.
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 Cisco vendor patch or upgrade to a fixed version of Cisco IPS/IDS as specified in the Cisco security advisory for CSCuq39550.
Fix this in Intrusion Prevention System
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-2014-3402 — 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-2014-3402 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