Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

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

45
This month
HIGH 7.5REMOTEUPGRADEUPGRADE

CVE-2016-6129 is a high-severity flaw (CVSS 7.5) affecting op-tee, libtomcrypt. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.8% (top 44%)
CISA exploited listNo
WeaknessCWE-20
Published2017-02-13
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: libtom · trustedfirmware

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

trustedfirmware op-tee UPGRADE
Affected: < 2.2.0
Fixed in: 2.2.0
Safe to downgrade to: no unaffected older release
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
libtom libtomcrypt UPGRADE
Affected: <= 1.17
Fixed in: newer than 1.17
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy libtomcrypt || rpm -q libtomcrypt || libtomcrypt --version
2. UPGRADE to newer than 1.17 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade libtomcrypt
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade libtomcrypt
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2016-6129?

op-tee: upgrade to 2.2.0; libtomcrypt: upgrade to newer than 1.17. Exact commands for each OS are on this page.

Is CVE-2016-6129 being exploited?

CVE-2016-6129 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2016-6129 affect?

CVE-2016-6129 affects op-tee, libtomcrypt. Severity is high (CVSS 7.5). 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 RS

How urgent is CVE-2016-6129?

Priority 45/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.