# CVE-2016-6096: Cross-site scripting in Key Lifecycle Manager

> Attackers can inject JavaScript into the Web UI to steal credentials from trusted sessions in IBM Key Lifecycle Manager.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **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:** 7 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r6q5-x9rc-mq2m

## What is CVE-2016-6096?

CVE-2016-6096 is a medium-severity cross-site scripting vulnerability in Ibm Security Key Lifecycle Manager, published on 7 Feb 2017. 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

IBM Tivoli Key Lifecycle Manager 2.0.1, 2.5, and 2.6 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.

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

## Which versions are affected by CVE-2016-6096?

It affects 2 products.


Products: Ibm Security Key Lifecycle Manager, Ibm Tivoli Key Lifecycle Manager.

## How do I fix CVE-2016-6096?

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

## Is CVE-2016-6096 being exploited?

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

## Other vulnerabilities in Ibm Security Key Lifecycle Manager

- [CVE-2017-1670](https://insights.sbomify.com/CVE-2017-1670/): SQL injection in Security Key Lifecycle Manager (critical 9.8)
- [CVE-2016-6093](https://insights.sbomify.com/CVE-2016-6093/): Weak cryptography in Security Key Lifecycle Manager (critical 9.8)
- [CVE-2016-6095](https://insights.sbomify.com/CVE-2016-6095/): Security feature bypass in Key Lifecycle Manager (critical 9.8)
- [CVE-2017-1672](https://insights.sbomify.com/CVE-2017-1672/): Cross-site request forgery in Security Key Lifecycle Manager (high 8.8)
- [CVE-2016-6103](https://insights.sbomify.com/CVE-2016-6103/): Cross-site request forgery in Key Lifecycle Manager (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6096 and fix it if it is affected.

What it is: CVE-2016-6096 is a medium-severity cross-site scripting vulnerability in Ibm Security Key Lifecycle Manager, published on 7 Feb 2017. 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-2016-6096 in the wild and no public exploit code.

Affected product: Ibm Security Key Lifecycle Manager. 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-2016-6096/ (Markdown: https://insights.sbomify.com/CVE-2016-6096/index.md)
```

## Sources

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

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