Ips Sensor SoftwareApplication · Cisco
CVE-2014-0720
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 · uneditedCisco 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 a flood of jumbo frames, aka Bug ID CSCuh94944.
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 confidenceCisco IPS Software versions 7.1 before 7.1(8)E4 and 7.2 before 7.2(2)E4 contain a vulnerability in the Analysis Engine process that crashes when receiving a flood of jumbo frames (frames larger than standard MTU size), allowing remote unauthenticated attackers to cause 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
Ips Sensor SoftwareApplication
<= 7.1\(1\)e4= 7.1\(2\)e4= 7.1\(3\)e4= 7.1\(4\)e4= 7.1\(6\)e4= 7.1\(7\)e4= 7.1\(8\)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.
-
Identify installed Cisco IPS Software versionLog into the IPS sensor CLI and run the command 'show version' or 'show module' to display the software version informationAffected if The displayed version is 7.1(1)E4 through 7.1(7)E4, or 7.1(8)E4, or 7.2(1)E4 - these fall within the vulnerable version range
-
Verify Analysis Engine process statusRun the command 'show engine' or 'show processes' in the IPS CLI to confirm the Analysis Engine is runningAffected if The Analysis Engine process is active - this is the component vulnerable to the jumbo frame crash
-
Confirm network exposure of IPS sensorReview network configuration to determine if the IPS sensor management interface or sensor ports are directly accessible from untrusted networksAffected if The IPS sensor can receive traffic from remote unauthenticated sources on its sensing interfaces - this is required for remote exploitation
-
Check for recent crash logsRun 'show log' or examine crash dump files for entries around the time of any observed service interruptionsAffected if The logs show Analysis Engine crashes with jumbo frame-related error messages, indicating possible exploitation
You are affected if your Cisco IPS Sensor runs version 7.1(1)E4 through 7.1(7)E4, 7.1(8)E4, or 7.2(1)E4, the Analysis Engine is active, and the sensor is exposed to remote network traffic carrying jumbo frames.
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. If immediate patching is not possible, consider implementing network filtering to limit jumbo frame traffic reaching the IPS sensor.
Fix this in Ips Sensor Software
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing6.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 $4,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0720 — 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-0720 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