CVE-2014-2142
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 ONS 15454 controller cards with software 10.0 and earlier allow remote attackers to cause a denial of service (card reload) via a crafted HTTP URI, aka Bug ID CSCun06870.
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 vulnerability exists in Cisco ONS 15454 controller cards running software version 10.0 or earlier. Attackers can trigger a denial of service by sending a specially crafted HTTP URI request to the affected device, causing the controller card to reload and interrupt services.
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= 9.0= 9.1= 9.2= 9.2.1= 9.2.2= 9.3= 9.4= 9.6<= 10.0= 9.8all versionsCVSS 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 ONS 15454 hardwareLog into the device or check inventory to confirm the device model is Cisco ONS 15454. This vulnerability affects controller cards in this specific optical networking platform.Affected if Device is not a Cisco ONS 15454 system - the vulnerability does not apply.
-
Retrieve software version from controller cardAccess the controller card CLI or web interface and retrieve the running software version. In the CLI, this is typically shown via 'show version' or similar command. The version appears as a number like 9.x or 10.x.Affected if Unable to retrieve version - verify access to the controller card.
-
Compare version against affected rangeCompare the installed version to the affected list: 9.0, 9.1, 9.2, 9.2.1, 9.2.2, 9.3, 9.4, 9.6, 9.8, or any version 10.0 or earlier.Affected if Version is 10.0 or earlier (9.0 through 10.0 inclusive) - the device is running a vulnerable version.
-
Verify HTTP service is enabledCheck the controller card configuration to see if HTTP or web management interface is enabled. This is typically found in the device web interface settings or via 'show running-config' looking for HTTP service configuration.Affected if HTTP is disabled or blocked, the attack surface may be reduced but the vulnerable code still exists in the software.
A user is affected if they have a Cisco ONS 15454 controller card running software version 10.0 or earlier with HTTP service enabled, as the specially crafted HTTP URI request can trigger a controller reload.
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 ONS 15454 controller card software to a version newer than 10.0 (e.g., 10.1 or later) that addresses this vulnerability. If upgrades are not immediately feasible, restrict HTTP access to these devices using network segmentation or firewall rules to prevent untrusted external access.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2142 — 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-2142 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