dbcve.org
Bladecenter Hs22 FirmwareOperating system · Lenovo

CVE-2019-6159

MEDIUM · 6.1 CVSS v3.1 Published 2019-08-19
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
A stored cross-site scripting (XSS) vulnerability exists in various firmware versions of the legacy IBM System x IMM (IMM v1) embedded Baseboard Management Controller (BMC). This vulnerability could allow an unauthenticated user to cause JavaScript code to be stored in the IMM log which may then be executed in the user's web browser when IMM log records containing the JavaScript code are viewed. The JavaScript code is not executed on IMM itself. The later IMM2 (IMM v2) is not affected.

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

A stored cross-site scripting (XSS) vulnerability exists in IBM System x IMM v1 embedded Baseboard Management Controller firmware. An unauthenticated attacker can inject malicious JavaScript code into the IMM log, which executes in the victim's browser when viewing the log entries.

MitigationApply available IBM firmware updates for IMM v1; if no patch exists, restrict network access to the BMC interface and disable remote web management or implement compensating controls such as browser-based filtering of log content.

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
Bladecenter Hs22 FirmwareOperating system
Affected:all versions
Bladecenter Hs22v FirmwareOperating system
Affected:all versions
Bladecenter Hx5 FirmwareOperating system
Affected:all versions
System X Idataplex Dx360 M2 FirmwareOperating system
Affected:all versions
System X Idataplex Dx360 M3 FirmwareOperating system
Affected:all versions
System X3400 M3 FirmwareOperating system
Affected:all versions
System X3500 M2 FirmwareOperating system
Affected:all versions
System X3500 M3 FirmwareOperating system
Affected:all versions

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.1/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. Identify the server model
    Run 'dmidecode -s system-product-name' or check system inventory to determine if the server is one of the affected models: Lenovo Bladecenter Hs22, Hs22v, Hx5, System X Idataplex Dx360 M2/M3, System X3400 M3, or System X3500 M2/M3
    Affected if The server model matches one of the listed affected products
  2. Check IMM firmware version
    Access the IMM web interface or run 'ipmitool -I lanplus -H <BMC_IP> -U ADMIN -P ADMIN raw command' to retrieve the IMM firmware version. Compare against the affected version range
    Affected if IMM v1 firmware is installed (all versions of the listed products are affected)
  3. Verify IMM web management interface is enabled
    Check if the IMM web interface is accessible by navigating to https://<BMC_IP> or running 'nmap -p 443,80 <BMC_IP>' to detect if web services are running on the BMC
    Affected if The IMM web interface is accessible and enabled, allowing log viewing via browser
  4. Inspect IMM logs for suspicious content
    Access the IMM web interface, navigate to the 'Event Log' or 'System Log' section. Look for unexpected JavaScript tags, script elements, or encoded content in log entries that was not generated by normal system events
    Affected if Log entries contain unescaped HTML, JavaScript, or script tags that could execute in a browser

If the server is one of the affected Lenovo models with IMM v1 firmware, the IMM web interface is enabled, and the logs contain executable script content, the environment is vulnerable to CVE-2019-6159.

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

Apply available IBM firmware updates for IMM v1; if no patch exists, restrict network access to the BMC interface and disable remote web management or implement compensating controls such as browser-based filtering of log content.

Fix this in Bladecenter Hs22 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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