dbcve.org
Power Hardware Management ConsoleApplication · Ibm

CVE-2014-0883

MEDIUM · 6.1 CVSS v3.0 Published 2018-04-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
IBM Power HMC 7.1.0 through 7.8.0 and 7.3.5 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.  IBM X-Force ID:  91163.

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

IBM Power HMC versions 7.1.0 through 7.8.0 and 7.3.5 contain a stored cross-site scripting (XSS) vulnerability in the web interface. An authenticated attacker can embed malicious JavaScript code that executes in the browsers of other users viewing the affected pages, potentially allowing session hijacking and credentials disclosure within trusted sessions.

MitigationUpdate IBM Power HMC to a patched version beyond 7.8.0, or apply the appropriate IBM fix. If immediate patching is not possible, implement input validation/sanitization on the web interface and consider restricting web UI access to trusted networks.

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
Power Hardware Management ConsoleApplication
Affected:= 7r7.1.0= 7r7.2.0= 7r7.3.0= 7r7.3.5= 7r7.4.0= 7r7.5.0= 7r7.6.0= 7r7.7.0= 7r7.8.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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Determine the installed IBM Power HMC version
    Access the HMC command line (via SSH or console) and run the version display command (commonly 'lshmc -V' or query the HMC properties through the management interface). Alternatively, the version is often displayed on the login page or in the HMC navigation panel when accessed via web browser.
    Affected if The displayed version matches 7.1.0, 7.2.0, 7.3.0, 7.3.5, 7.4.0, 7.5.0, 7.6.0, 7.7.0, or 7.8.0.
  2. Confirm the HMC web interface is enabled and accessible
    Attempt to access the HMC web interface by navigating to the HMC IP address or hostname over HTTPS (for example, https://hmc_hostname). Verify the login page loads successfully.
    Affected if The web interface is reachable and displays a login prompt, indicating it is enabled.
  3. Verify user authentication is possible
    Log in to the HMC web interface with a valid user account (or confirm that user accounts exist and can authenticate).
    Affected if Authenticated users can access the web interface, as the vulnerability requires an authenticated attacker to inject the malicious script.
  4. Identify if the vulnerable page inputs are in use
    After logging in, navigate through common HMC web pages such as user management, system settings, or resource management panels where user-supplied data may be stored and displayed (for example, custom labels, descriptions, or notes fields).
    Affected if Any fields exist that accept user input and display it back to other users without sanitization, creating the condition for stored XSS to execute.

Your environment is affected if the IBM Power HMC version is 7.1.0 through 7.8.0 (including 7.3.5) and the web interface is enabled and accessible to authenticated users.

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

Update IBM Power HMC to a patched version beyond 7.8.0, or apply the appropriate IBM fix. If immediate patching is not possible, implement input validation/sanitization on the web interface and consider restricting web UI access to trusted networks.

Fix this in Power Hardware Management Console Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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 locally
dbcve dependency scanner

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