What is CVE-2017-15361?A medium-severity flaw in Trusted Platform Firmware, explained.
CVE-2017-15361 is a medium-severity flaw (CVSS 5.9) in Trusted Platform Firmware from Infineon, published on 16 October 2017. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 9.8%. If you run an affected version, plan in the vendor’s fix.
Published 16 October 2017. Record last updated 20 April 2025. We keep this page's data up to date.
What is CVE-2017-15361? In plain terms.
It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data.
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.
What kind of flaw is it?
- UnknownUnknown
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offHard: conditions must line up
- Login needed firstNo login needed
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan read data
Severity vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Is CVE-2017-15361 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 9.8%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
- Exploit likelihood fell
- Exploit likelihood jumped
CVE-2017-15361 scores 42. Action: Plan remediation.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2017-15361 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2017-15361? 126 products.
The published record lists 126 products from 35 vendors. If you run one of these, check your version, then go to the fix below.
- Operating system
Trusted Platform Firmware
by Infineon
Affected versions4.314.326.40133.32 - Hardware
100s Chromebook
by Lenovo
Affected versionsversion not specified - Hardware
Akoya S2013
by Medion
Affected versionsversion not specified - Hardware
C1101 Chromebook
by Senkatel
Affected versionsversion not specified - Hardware
C720 Chromebook
by Acer
Affected versionsversion not specified - Hardware
Chromebase
by Acer
Affected versionsversion not specified - Hardware
Chromebase
by Aopen
Affected versionsversion not specified - Hardware
Chromebase 22cb25s
by Lg
Affected versionsversion not specified - Hardware
Chromebase 22cv241
by Lg
Affected versionsversion not specified
How do I fix CVE-2017-15361? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
Does CVE-2017-15361 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
The Infineon RSA library 1.02.013 in Infineon Trusted Platform Module (TPM) firmware, such as versions before 0000000000000422 - 4.34, before 000000000000062...
- Matched to
- Trusted Platform Firmware on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2017-15361 is a medium-severity flaw in Trusted Platform Firmware from Infineon, published on 16 October 2017. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data.
It scores 5.9 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2017-15361 is 42 out of 100, which is Medium. Its action is "Plan remediation". No sign of exploitation and a low forecast. Patch it in your normal update cycle.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 9.8%. That can change at any time, which is why we keep watching.
For Trusted Platform Firmware from Infineon: 4.31, 4.32, 6.40, 133.32. The record lists 126 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.