dbcve.org
Integrated Management Controller SupervisorApplication · Cisco

CVE-2015-6259

HIGH · 9.4 CVSS v2.0 Published 2015-09-04
Fix available
A fix is available. Upgrade to after 5.2.0.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
The JavaServer Pages (JSP) component in Cisco Integrated Management Controller (IMC) Supervisor before 1.0.0.1 and UCS Director (formerly Cloupia Unified Infrastructure Controller) before 5.2.0.1 allows remote attackers to write to arbitrary files via crafted HTTP requests, aka Bug IDs CSCus36435 and CSCus62625.

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 confidence

The JSP component in Cisco IMC Supervisor before 1.0.0.1 and UCS Director before 5.2.0.1 contains an arbitrary file write vulnerability that allows remote unauthenticated attackers to write files to arbitrary locations on the filesystem via crafted HTTP requests.

MitigationApply the vendor patches by upgrading to IMC Supervisor 1.0.0.1 or later and UCS Director 5.2.0.1 or later to remediate this arbitrary file write 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
Integrated Management Controller SupervisorApplication
Affected:<= 1.0.0.0
Unified Computing System DirectorApplication
Affected:<= 5.2.0.0= 3.4_base= 4.0_base= 4.1_base= 5.0.0.0= 5.0.0.1= 5.0.0.2= 5.0.0.3= 5.1.0.0= 5.1.0.1

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
Authentication
None
Confidentiality
None
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:N/I:C/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 checks

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

  1. Identify installed product
    Determine whether Cisco IMC Supervisor or Cisco UCS Director is deployed in your environment. Check product documentation or web interface login page for product name.
    Affected if Product is Cisco IMC Supervisor or Cisco UCS Director
  2. Check IMC Supervisor version
    Access the IMC Supervisor web interface and navigate to the About or Administration section to view the installed version number.
    Affected if Version is 1.0.0.0 or earlier
  3. Check UCS Director version
    Access the UCS Director web interface and navigate to the About or Administration section to view the installed version number.
    Affected if Version is 5.2.0.0 or earlier, or matches one of these base versions: 3.4_base, 4.0_base, 4.1_base, 5.0.0.0, 5.0.0.1, 5.0.0.2, 5.0.0.3, 5.1.0.0, or 5.1.0.1
  4. Verify JSP endpoint accessibility
    From an external perspective, determine if the JSP component endpoint is reachable over the network on the HTTP/HTTPS ports used by the product.
    Affected if The JSP interface is exposed to network without proper authentication restrictions
  5. Review access logs for suspicious file write attempts
    Examine HTTP access logs for unusual POST requests to JSP endpoints with file path parameters or unexpected payload patterns.
    Affected if Logs show unauthenticated requests attempting to write files to unusual paths

Your environment is affected if you are running Cisco IMC Supervisor version 1.0.0.0 or earlier, or Cisco UCS Director version 5.2.0.0 or earlier (including the specific base versions listed), and the JSP component is network-accessible.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 5.2.0.0
Interim mitigation

Apply the vendor patches by upgrading to IMC Supervisor 1.0.0.1 or later and UCS Director 5.2.0.1 or later to remediate this arbitrary file write vulnerability.

Recommended fix High confidence

IMC Supervisor 1.0.0.1 or UCS Director 5.2.0.1

  1. Back up all current configurations and data for the Cisco IMC Supervisor or UCS Director system
  2. Download the fixed version (1.0.0.1 for IMC Supervisor or 5.2.0.1 for UCS Director) from Cisco's official download channels
  3. Review Cisco's release notes and upgrade documentation for the specific version before proceeding
  4. Follow Cisco's documented upgrade procedure for the respective product, ensuring proper downtime planning
  5. After upgrade, verify the system is running the patched version and confirm the JSP input validation vulnerability is resolved
  6. Validate that existing workflows and integrations continue to function correctly post-upgrade
Caveat Review Cisco release notes for version-specific changes; some interface or workflow modifications may occur between major versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Integrated Management Controller Supervisor Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA5.0 h
33.0 hours of engineering $5,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-6259 — 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-2015-6259 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