dbcve.org
Unified Computing System DirectorApplication · Cisco

CVE-2018-15404

MEDIUM · 6.5 CVSS v3.0 Published 2018-10-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A vulnerability in the web interface of Cisco Integrated Management Controller (IMC) Supervisor and Cisco UCS Director could allow an authenticated, remote attacker to cause a denial of service (DoS) condition on an affected system. The vulnerability is due to insufficient restrictions on the size or total amount of resources allowed via the web interface. An attacker who has valid credentials for the application could exploit this vulnerability by sending a crafted or malformed HTTP request to the web interface. A successful exploit could allow the attacker to cause oversubscription of system resources or cause a component to become unresponsive, resulting in a DoS condition.

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 confidence

The web interfaces of Cisco IMC Supervisor and Cisco UCS Director lack proper restrictions on resource consumption, allowing authenticated attackers to send malformed HTTP requests that overconsume system resources, causing denial of service.

MitigationImplement resource limits and input validation on the web interface to restrict request sizes and rates; apply available Cisco patches for this vulnerability.

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 System DirectorApplication
Affected:= 6.6\(0.0\)
Integrated Management Controller SupervisorApplication
Affected:= 2.1\(0.0\)

CVSS 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
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Cisco product
    Check system for presence of Cisco Integrated Management Controller Supervisor or Cisco Unified Computing System Director. Query installed packages or check application directories for these product names.
    Affected if Neither product is installed (not affected)
  2. Determine installed version of Cisco UCS Director
    Use command line or web interface to query the version of Cisco UCS Director. Common methods: check the About page in the web GUI, or use CLI command 'show version' if SSH access is available.
    Affected if Version equals 6.6(0.0)
  3. Determine installed version of Cisco IMC Supervisor
    Use command line or web interface to query the version of Cisco IMC Supervisor. Common methods: check the About page in the web GUI, or use CLI command 'show version' if SSH access is available.
    Affected if Version equals 2.1(0.0)
  4. Verify web interface is accessible
    Check if the web management interface is exposed and reachable. Attempt to access the HTTPS management portal or check network listener status for HTTP/HTTPS ports (typically 443 or 8443).
    Affected if Web interface is enabled and accessible (required for exploitation)
  5. Check for existing resource limit configurations
    Inspect web server configuration files or management interface settings for any rate limiting, request size limits, or resource consumption restrictions. Look for configuration parameters related to request throttling or max request size.
    Affected if No resource limits are configured on the web interface

User is affected if either Cisco UCS Director version 6.6(0.0) or Cisco IMC Supervisor version 2.1(0.0) is running AND the web management interface is exposed without resource limits configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement resource limits and input validation on the web interface to restrict request sizes and rates; apply available Cisco patches for this vulnerability.

Fix this in Unified Computing System Director Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-15404 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-15404 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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