# CVE-2017-1666: XML external entity in Security Key Lifecycle Manager

> Remote attackers can exploit XML External Entity injection in IBM Tivoli Key Lifecycle Manager to expose sensitive information or cause memory exhaustion.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jan 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-hm3g-xjp2-hw8q

## What is CVE-2017-1666?

CVE-2017-1666 is a high-severity vulnerability in Ibm Security Key Lifecycle Manager, published on 9 Jan 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Tivoli Key Lifecycle Manager 2.5, 2.6, and 2.7 is vulnerable to a XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources. IBM X-Force ID: 133540.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

## Which versions are affected by CVE-2017-1666?

It affects 1 product.


Products: Ibm Security Key Lifecycle Manager.

## How do I fix CVE-2017-1666?

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

## Is CVE-2017-1666 being exploited?

There is no known exploitation of CVE-2017-1666 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-2017-1666 and fix it if it is affected.

What it is: CVE-2017-1666 is a high-severity vulnerability in Ibm Security Key Lifecycle Manager, published on 9 Jan 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-1666 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-2017-1666/ (Markdown: https://insights.sbomify.com/CVE-2017-1666/index.md)
```

## Sources

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

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