Skip to content
Fencer Vulns
high 7.5

CVE-2016-6129 json

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 len…

published 2017-02-13 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-7063

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 55%
public exploits
0
none known

Summary

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.

Patch / fix

  • trustedfirmware op-tee 2.2.0
  • libtomcrypt Debian 14, Debian 13, Debian 12 1.17-8

debian advisories DEBIAN-CVE-2016-6129

  • libtomcrypt Ubuntu 14.04 LTS 1.17-5ubuntu0.1
  • libtomcrypt Ubuntu 16.04 LTS 1.17-7ubuntu0.1

ubuntu advisories UBUNTU-CVE-2016-6129

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2016-6129 updated cvss 4.8

libtomcrypt: possible OP-TEE Bleichenbacher attack

  • Red Hat Enterprise Linux 7 libtomcrypt Red Hat Virtualization 4 libtomcrypt
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.77% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.