Ons 15454Hardware / appliance · Cisco
CVE-2013-6703
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 TLS/SSLv3 module on Cisco ONS 15454 controller cards allows remote attackers to cause a denial of service (card reset) via crafted (1) TLS or (2) SSLv3 packets, aka Bug ID CSCuh34787.
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 confidenceA denial of service vulnerability exists in the TLS/SSLv3 module of Cisco ONS 15454 controller cards. Remote attackers can send malformed TLS or SSLv3 packets that trigger a card reset, causing service disruption.
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 15454Hardware / appliance
all 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
- 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.
-
Confirm Cisco ONS 15454 device presenceIdentify if any node in your network is a Cisco ONS 15454 device. This is typically found in optical transport network inventory or device management records. Check device model numbers or serial numbers against the ONS 15454 product line.Affected if The environment contains any Cisco ONS 15454 controller cards.
-
Verify TLS/SSLv3 service availabilityDetermine if the TLS or SSLv3 protocol service is enabled on the Cisco ONS 15454 controller card. This is typically configurable in the card's security or protocol settings. Consult the device documentation for your specific version to locate TLS/SSL configuration.Affected if TLS or SSLv3 is enabled and accessible on the ONS 15454 controller card.
-
Assess network exposure of the TLS/SSL serviceIdentify whether the TLS/SSLv3 service ports on the ONS 15454 are directly reachable from untrusted networks. Check firewall rules, ACLs, and network topology to determine if the device management or optical channel interfaces accepting TLS/SSL traffic are exposed to external attackers.Affected if The TLS/SSLv3 service on the ONS 15454 is reachable from networks outside your trusted administrative zone.
If you have a Cisco ONS 15454 device with TLS or SSLv3 enabled and that service is network-accessible to untrusted parties, your environment is affected by this CVE.
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 dataApply the relevant Cisco software update/patch for CSCuh34787. If no patch is available, consider network-level filtering of malformed SSL/TLS traffic or network segmentation to limit exposure.
Fix this in Ons 15454
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6703 — 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-2013-6703 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