Ips Sensor SoftwareApplication · Cisco
CVE-2014-0718
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 produce-verbose-alert feature in Cisco IPS Software 7.1 before 7.1(8)E4 and 7.2 before 7.2(2)E4 allows remote attackers to cause a denial of service (Analysis Engine process outage) via fragmented packets, aka Bug ID CSCui91266.
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 produce-verbose-alert feature in Cisco IPS (Intrusion Prevention System) Software contains a vulnerability where specially crafted fragmented packets sent by remote attackers can cause the Analysis Engine process to fail, resulting in a denial of service condition. This affects Cisco IPS versions 7.1 before 7.1(8)E4 and 7.2 before 7.2(2)E4.
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
Ips Sensor SoftwareApplication
= 7.1\(4\)e4= 7.1\(5\)e4= 7.1\(6\)e4= 7.1\(7\)e4= 7.2\(1\)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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Cisco IPS software versionLog into the Cisco IPS manager or CLI and retrieve the current software version using the 'show version' or 'show module' commandAffected if The version is 7.1(4)E4, 7.1(5)E4, 7.1(6)E4, 7.1(7)E4, 7.2(1)E4, or any 7.1.x version before 7.1(8)E4 or 7.2.x version before 7.2(2)E4
-
Verify the produce-verbose-alert feature is enabledAccess the IPS sensor configuration and check if the produce-verbose-alert setting is turned on. This is typically found in the IPS policy configuration under alert settingsAffected if The produce-verbose-alert feature is enabled in the IPS policy configuration
-
Confirm Analysis Engine process statusUse the 'show process' or 'show engine' command in the Cisco IPS CLI to check the status of the Analysis Engine processAffected if The Analysis Engine process is running and vulnerable to the DoS condition from fragmented packets
You are affected if you are running a Cisco IPS version 7.1 before 7.1(8)E4 or 7.2 before 7.2(2)E4 AND have the produce-verbose-alert feature enabled, as this specific feature must be active for the specially crafted fragmented packets to trigger the Analysis Engine denial of service.
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 IPS Software to version 7.1(8)E4 or 7.2(2)E4 or later to remediate this vulnerability. As a network security device vulnerability with DoS impact, prioritize patching given the CVSS 7.1 severity rating.
Fix this in Ips Sensor Software
Scoped from the published advisory
- Consultation3.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0718 — 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-0718 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