dbcve.org
Intrusion Prevention SystemApplication · Cisco

CVE-2014-3406

HIGH · 7.1 CVSS v2.0 Published 2014-10-19
Fix available
A fix is available. Upgrade to after 7.1 or later.
See remediation →
80/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
Race condition in the IP logging feature in Cisco Intrusion Prevention System (IPS) Software 7.1(7)E4 and earlier allows remote attackers to cause a denial of service (device reload) via crafted IP traffic that matches a problematic rule, aka Bug ID CSCud82085.

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 confidence

A race condition exists in the IP logging feature of Cisco IPS Software 7.1(7)E4 and earlier. When remote attackers send crafted IP traffic that matches a specific problematic rule, the race condition triggers, causing the IPS device to reload, resulting in denial of service.

MitigationUpgrade Cisco IPS Software to a version beyond 7.1(7)E4 that includes the fix for CSCud82085. Until then, consider disabling the problematic rule or implementing network-level filtering to block the malicious traffic patterns.

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
Affected:<= 7.1\(7\)e4

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
M
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:M/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. Check Cisco IPS Software version
    Log into the IPS CLI and run 'show version' or 'show module' to display the installed software version. Compare against the affected range: 7.1(7)E4 and earlier.
    Affected if The installed version is 7.1(7)E4 or any version number lower than 7.1(7)E4
  2. Verify IP logging feature status
    In the IPS CLI, run 'show ip-logging' or check the IPS manager interface for IP logging configuration status.
    Affected if IP logging is enabled and actively logging traffic
  3. Identify active signature rules that trigger IP logging
    Use 'show signatures' or access the IPS manager to list all active signature rules. Look for any rules that enable IP logging when triggered by matching traffic.
    Affected if Any signature rules that invoke IP logging are enabled and active

Your environment is affected if you are running Cisco IPS Software version 7.1(7)E4 or earlier AND have IP logging enabled with active rules that trigger IP packet logging.

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
Upgrade available Upgrade to a release after 7.1
Interim mitigation

Upgrade Cisco IPS Software to a version beyond 7.1(7)E4 that includes the fix for CSCud82085. Until then, consider disabling the problematic rule or implementing network-level filtering to block the malicious traffic patterns.

Fix this in Intrusion Prevention System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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