# CVE-2017-15361: Weak cryptography in n/a

> Flawed RSA key generation in Infineon TPM firmware allows attackers to break cryptographic protections and access encrypted data.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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:** 16 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qcrq-wp7v-84jc, MGASA-2017-0395

## What is CVE-2017-15361?

CVE-2017-15361 is a medium-severity vulnerability in n/a, published on 16 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Infineon RSA library 1.02.013 in Infineon Trusted Platform Module (TPM) firmware, such as versions before 0000000000000422 - 4.34, before 000000000000062b - 6.43, and before 0000000000008521 - 133.33, mishandles RSA key generation, which makes it easier for attackers to defeat various cryptographic protection mechanisms via targeted attacks, aka ROCA. Examples of affected technologies include BitLocker with TPM 1.2, YubiKey 4 (before 4.3.5) PGP key generation, and the Cached User Data encryption feature in Chrome OS.

## Which versions are affected by CVE-2017-15361?

It affects 2 products.


Products: Infineon Rsa Library, Infineon Trusted Platform Firmware.

## How do I fix CVE-2017-15361?

Apply the vendor's patch.

## Is CVE-2017-15361 being exploited?

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

Public exploit code:

- Detects Windows and Linux systems with enabled Trusted Platform Modules (TPM) vulnerable to CVE-2017-15361. #nsacyber (github_poc): https://github.com/nsacyber/Detect-CVE-2017-15361-TPM
- Go package that checks if RSA keys are vulnerable to ROCA / CVE-2017-15361 (github_poc): https://github.com/titanous/rocacheck
- Bro plugin to check if certificates are affected by CVE-2017-15361 (github_poc): https://github.com/0xxon/zeek-plugin-roca
- Simple PowerShell script to check whether a computer is using an Infineon TPM chip that is vulnerable to CVE-2017-15361. (github_poc): https://github.com/lva/Infineon-CVE-2017-15361
- Reimplementation of CVE-2017-15361 checker in C (github_poc): https://github.com/0xxon/roca
- ROCA attack on vulnerability CVE-2017-15361 (github_poc): https://github.com/Elbarbons/ROCA-attack-on-vulnerability-CVE-2017-15361

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-15361 and fix it if it is affected.

What it is: CVE-2017-15361 is a medium-severity vulnerability in n/a, published on 16 Oct 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-2017-15361 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-2017-15361/ (Markdown: https://insights.sbomify.com/CVE-2017-15361/index.md)
```

## Sources

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

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