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 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.

Published: 2017-02-13 Last update: 2026-06-05 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2016-6129 is rated Moderate Risk (44.1/100): CVSS High severity, with low exploitation likelihood (EPSS 0.18%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2016-6129

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-06 0.14% 0.18% +0.04%
2 2025-04-14 0.15% 0.14% -0.01%
3 2025-03-30 — 0.15% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2016-6129

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:N/I:P/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2016-6129

OS Trackers for CVE-2016-6129

vendor priority summary link
debian not yet assigned CVE-2016-6129 not yet assigned priority: Debian including 1 source packages (libtomcrypt), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2016-6129
redhat medium — https://access.redhat.com/security/cve/CVE-2016-6129
ubuntu medium CVE-2016-6129 medium priority: Ubuntu including 1 source packages (libtomcrypt), 8 status rows across 8 suites (artful, bionic, precise, trusty, upstream, xenial, yakkety, zesty): ignored 3, released 3, needs-triage 1, not-affected 1. https://ubuntu.com/security/CVE-2016-6129

Affected software / configurations for CVE-2016-6129

Vendor Product Version Raw CPE
trustedfirmware op-tee < 2.2.0 cpe:2.3:o:trustedfirmware:op-tee:*:*:*:*:*:*:*:*
libtom libtomcrypt <= 1.17 cpe:2.3:a:libtom:libtomcrypt:*:*:*:*:*:*:*:*

References for CVE-2016-6129

cvelogic Threat Intelligence