Ips Sensor SoftwareApplication · Cisco
CVE-2014-0719
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 control-plane access-list implementation in Cisco IPS Software before 7.1(8p2)E4 and 7.2 before 7.2(2)E4 allows remote attackers to cause a denial of service (MainApp process outage) via crafted packets to TCP port 7000, aka Bug ID CSCui67394.
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 confidenceA denial of service vulnerability exists in Cisco IPS Software control-plane access-list implementation. Remote attackers can send crafted packets to TCP port 7000, causing the MainApp process to crash and resulting in IPS failure. Affected versions are before 7.1(8p2)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\(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
- 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 Cisco IPS Sensor Software versionRun the 'show version' command on the IPS sensor CLI or retrieve the version through the IPS Manager Express or Cisco IPS CLI. Compare the version number against the affected ranges: 7.1(1)E4 through 7.1(8)E4, or 7.2(1)E4.Affected if The installed version is 7.1(x)E4 where x is 1-8, or 7.2(1)E4.
-
Confirm TCP port 7000 is reachableVerify if TCP port 7000 is open and accessible on the management interface by attempting a connection from an external system or reviewing firewall/access-list rules that permit traffic to this port.Affected if TCP port 7000 is exposed to untrusted networks or accessible from outside the management network.
-
Check if control-plane access-list is configuredExamine the IPS sensor configuration for any control-plane access-list entries using the 'show run' command or reviewing the access-list settings in the IPS management interface.Affected if A control-plane access-list is configured on the sensor.
You are affected if your Cisco IPS Sensor Software version is 7.1(1-8)E4 or 7.2(1)E4 AND TCP port 7000 is accessible on your management interface.
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(8p2)E4 or 7.2(2)E4 or later to patch the vulnerability. As an interim measure, consider blocking or rate-limiting untrusted access to TCP port 7000 on the management interface.
Fix this in Ips Sensor Software
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,216.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0719 — 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-0719 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