Unified Computing SystemOperating system · Cisco
CVE-2015-6415
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 Unified Computing System (UCS) 2.2(3f)A on Fabric Interconnect 6200 devices allows remote attackers to cause a denial of service (CPU consumption or device outage) via a SYN flood on the SSH port during the booting process, aka Bug ID CSCuu81757.
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 confidenceCisco UCS Fabric Interconnect 6200 devices running version 2.2(3f)A are vulnerable to SYN flood attacks targeting the SSH port specifically during the device booting process. Attackers can send malicious SYN packets to exhaust CPU resources or cause complete device outage, resulting in 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
Unified Computing SystemOperating system
= 2.2\(3f\)aCVSS 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 the device modelLog into the Cisco UCS Manager or use the 'show inventory' command on the Fabric Interconnect CLI to confirm the hardware model is Cisco UCS Fabric Interconnect 6200 SeriesAffected if The device is not a Cisco UCS Fabric Interconnect 6200 series device, then it is not affected by this specific CVE
-
Check the installed firmware versionUse the 'show version' command on the Fabric Interconnect CLI or check the firmware version through UCS Manager under the Fabric Interconnect firmware summaryAffected if The installed firmware version is exactly 2.2(3f)A (note: other versions in the 2.2 branch may have different patch status, but this specific version is confirmed vulnerable)
-
Verify SSH service configurationCheck if SSH is enabled on the Fabric Interconnect by running 'show ssh server' or reviewing the service profile configuration in UCS ManagerAffected if SSH service is enabled and listening on the device, which is required for the SYN flood to target the SSH port during boot
-
Assess network accessibility of SSH portPerform a port scan or check access control lists to determine if TCP port 22 (SSH) is reachable from external or untrusted networksAffected if SSH port 22 is exposed to network segments where malicious SYN packets could be sent during the device booting process
A device is affected if it is a Cisco UCS Fabric Interconnect 6200 running firmware version 2.2(3f)A with SSH enabled and accessible from a network where an attacker could send SYN packets during the boot sequence.
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 Cisco patch for bug CSCuu81757 (firmware update) and implement upstream network-level SYN flood protection or rate limiting on perimeter firewalls/switches until the patch can be deployed.
Fix this in Unified Computing System
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6415 — 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-6415 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