# CVE-2019-6159: Cross-site scripting in legacy System x IMM (IMM v1) firmware

> An unauthenticated attacker can inject JavaScript into the IMM log, which executes in the victim's browser when viewing logs.

- **Severity:** Critical 9.6 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Aug 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qhp9-p4pv-36mj

## What is CVE-2019-6159?

CVE-2019-6159 is a critical cross-site scripting vulnerability in IBM legacy System x IMM (IMM v1) firmware, published on 19 Aug 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2019-6159?

It affects 15 products.


Products: Lenovo Bladecenter Hs22 Firmware, Lenovo Bladecenter Hs22v Firmware, Lenovo Bladecenter Hx5 Firmware, Lenovo System X3400 M3 Firmware, Lenovo System X3500 M2 Firmware, Lenovo System X3500 M3 Firmware, Lenovo System X3550 M3 Firmware, Lenovo System X3560 M2 Firmware, Lenovo System X3630 M3 Firmware, Lenovo System X3650 M3 Firmware, Lenovo System X3690 X5 Firmware, Lenovo System X3850 X5 Firmware, Lenovo System X3950 X5 Firmware, Lenovo System X Idataplex Dx360 M2 Firmware, Lenovo System X Idataplex Dx360 M3 Firmware.

## How do I fix CVE-2019-6159?

No fix has been published for CVE-2019-6159 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-6159 being exploited?

There is no known exploitation of CVE-2019-6159 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-6159 and fix it if it is affected.

What it is: CVE-2019-6159 is a critical cross-site scripting vulnerability in IBM legacy System x IMM (IMM v1) firmware, published on 19 Aug 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-6159 in the wild and no public exploit code.

Affected product: IBM legacy System x IMM (IMM v1) firmware. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-6159/ (Markdown: https://insights.sbomify.com/CVE-2019-6159/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-6159
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-6159
- OSV: https://osv.dev/vulnerability/CVE-2019-6159

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-6159/
Summaries are generated and may contain mistakes; the official description above is the record.