# CVE-2016-6129: Other in n/a

> Attackers can forge RSA signatures or certificates in LibTomCrypt due to missing length validation, compromising authentication integrity.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-6129, DLA-612-1, MGASA-2016-0369, UBUNTU-CVE-2016-6129

## What is CVE-2016-6129?

CVE-2016-6129 is a high-severity vulnerability in n/a, published on 13 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2016-6129?

It affects 2 products.


Products: Libtom Libtomcrypt, Trustedfirmware Op-Tee.

## How do I fix CVE-2016-6129?

Upgrade to a fixed version.

## Is CVE-2016-6129 being exploited?

There is no known exploitation of CVE-2016-6129 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-12437](https://insights.sbomify.com/CVE-2018-12437/): Information disclosure in n/a (medium 4.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6129 and fix it if it is affected.

What it is: CVE-2016-6129 is a high-severity vulnerability in n/a, published on 13 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-6129 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-6129/ (Markdown: https://insights.sbomify.com/CVE-2016-6129/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-6129
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-6129
- OSV: https://osv.dev/vulnerability/CVE-2016-6129

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-6129/
Summaries are generated and may contain mistakes; the official description above is the record.