Ons 15454 System SoftwareOperating system · Cisco
CVE-2015-0765
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 System Software 10.30 and 10.301 allows remote attackers to cause a denial of service (tNetTask CPU consumption or card reset) via a flood of (1) IP or (2) Ethernet traffic, aka Bug ID CSCus57263.
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 confidenceThis is a denial of service vulnerability in Cisco ONS 15454 optical networking devices running software versions 10.30 and 10.301. Attackers can trigger the vulnerability by flooding the device with IP or Ethernet traffic, causing the tNetTask process to consume excessive CPU resources or forcing a card reset. The vulnerability stems from improper handling of high volumes of network traffic.
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
Ons 15454 System SoftwareOperating system
= 10.30= 10.301CVSS 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.
-
Confirm device model is Cisco ONS 15454Identify the hardware model through device inventory, CLI command 'show version', or network documentation. This vulnerability only affects the ONS 15454 optical networking platform.Affected if The device is not a Cisco ONS 15454 system
-
Check software version equals 10.30 or 10.301Use the CLI command 'show version' or access the TMS/CTC interface to view the installed software version. Compare against the affected versions 10.30 and 10.301.Affected if The installed software version is exactly 10.30 or 10.301
-
Verify network interfaces are activeUse the CLI command 'show ip interface brief' or check the device management interface status to confirm IP or Ethernet interfaces are enabled and configured.Affected if Network interfaces are active and the device is reachable on the network
-
Check for tNetTask high CPU or card resetsUse the CLI command 'show processes cpu history' or 'show logging' to examine for tNetTask process consuming excessive CPU, or look for recent card reset events in the system logs.Affected if tNetTask process shows unusually high CPU usage or recent unexplained card resets occur
A user is affected if the device is a Cisco ONS 15454 running software version 10.30 or 10.301, has active network interfaces, and exhibits tNetTask high CPU or unexplained card resets.
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 dataImplement network-level traffic filtering or rate limiting to block malicious traffic floods before reaching affected devices. Contact Cisco for available software updates that address this vulnerability.
Fix this in Ons 15454 System Software
Scoped from the published advisory
- 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-2015-0765 — 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-2015-0765 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