SecPod

Learn Search

Search across all Learn content

← Back to Security Research
ROCA: RSA Encryption Vulnerability

ROCA: RSA Encryption Vulnerability

Oct 29, 2017By Rinu K4 min read

Source: thehackernews.com

Return of Coppersmith’s Attack,

ROCA Attack

CVE-2017-15361

Infineon’s Trusted Platform Module

vulnerability management software

The fundamental property in public key cryptography is that public keys are really public. It provides anyone without causing any impact on security. This fundamental property is completely failing by the ROCA attack. The vulnerability arises from a software library Infineon Technologies AG used in cryptographic hardware for RSA key generation. All keys generated using this library are prone to ROCA attacks. This library uses various hardware many domains use, including trusted boot devices, electronic citizen documents, software package signing, TLS/HTTPS keys, authentication tokens, and PGP. Vulnerability Management tool can reduce these vulnerabilities.

This vulnerability is present in the library in use by NIST FIPS 140-2 and CC EAL5+, two internationally adopting cryptographic standards. It can be characterized by a specific structure of the generated RSA primes, which makes factorization practically possible for commonly used key lengths, including 1024 and 2048 bits. No physical access to the affected device is required, and only the knowledge of a public key is necessary. The primes generated allow for fast detection of vulnerable keys, even in large datasets. The key length ranges considered practically factorizable are 512 to 704 bits, 992 to 1216 bits, and 1984 to 2144 bits. 4096-bit RSA key is not practically factorizable now, but it can be possible if the attack is improving on its own.

Affected Versions:

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.

Impact:

An attacker can compute a valid private key from the value of a public key based only on a certificate. This makes everything possible. The private key can be misused to do anything on your behalf including encrypting traffic, decrypting the traffic, and impersonating the website and other related attacks. Usage scenario, availability of the public keys, and the lengths of keys used are the three main factors determining the actual impact of the vulnerability.

The usage domains affected by ROCA:

Source: securityaffairs.co

electronic citizen documents, authentication tokens, trusted boot devices, software package signing, TLS/HTTPS keys, and PGP

Detection:

The detection is finding the usage of a chip with a vulnerable library. However, The only reliable and recommended way is RSA key pair generation on the device and testing the public key against the ROCA flaw with the provided tools mentioned below,

  • Offline: https://github.com/crocs-muni/roca
  • https://keytester.cryptosense.com/
  • https://keychest.net/roca

Solution:

Fixed TPM firmware versions are as follows, upgrade to the latest as soon as possible.

  • 0000000000000422 – 4.34
  • 000000000000062b – 6.43
  • 0000000000008521 – 133.33

Protection:

Due to the complexity of this issue, it’s difficult to patch completely, but there are few mitigation methods. Windows users can address this issue by applying security updates issued by Microsoft. Google, HP, and Lenovo have also released some mitigation methods and firmware updates for their software products. The below-mentioned links describe the mitigation strategies and fixed version details provided by different vendors.

SanerNow detects these vulnerabilities and automatically fixes it by applying security updates for Windows users. Therefore, Download Saner now and keep your systems updated and secure.

Featured Posts

Open CVE-2026-31431: From 732 Bytes to Root - Anatomy of a Modern Linux Privilege Escalation

CVE-2026-31431: From 732 Bytes to Root - Anatomy of a Modern Linux Privilege Escalation

CVE Research

CVE-2026-31431: From 732 Bytes to Root - Anatomy of a Modern Linux Privilege Escalation

Jun 24, 2026

Open CVE-2026-31431: The Nine-Year Kernel Bug Hiding in Plain Sight

CVE-2026-31431: The Nine-Year Kernel Bug Hiding in Plain Sight

CVE Research

CVE-2026-31431: The Nine-Year Kernel Bug Hiding in Plain Sight

Jun 23, 2026

Open Squidbleed: A 29-Year-Old Squid Proxy Flaw That Leaks Cleartext HTTP Requests
Squidbleed: A 29-Year-Old Squid Proxy Flaw That Leaks Cleartext HTTP Requests

CVE Research

Squidbleed: A 29-Year-Old Squid Proxy Flaw That Leaks Cleartext HTTP Requests

Jun 23, 2026

Open AryStinger Malware Leverages 4,300+ Legacy Routers to Establish Persistent Spy Infrastructure
AryStinger Malware Leverages 4,300+ Legacy Routers to Establish Persistent Spy Infrastructure

CVE Research

AryStinger Malware Leverages 4,300+ Legacy Routers to Establish Persistent Spy Infrastructure

AryStinger represents a calculated shift in IoT threat methodology, abandoning noisy, destructive payloads in favor of silent, long-term reconnaissance infrastructure. By exploiting unpatched, end-of-life routers and NAS devices through decade-old vulnerabilities, the threat operator has assembled a distributed fleet of over 4,300 Executor nodes capable of conducting parallelized DNS enumeration, port scanning, and service fingerprinting at scale, all while masking origin behind residential IP addresses. With active development ongoing and a potential operational timeline stretching back to 2024, AryStinger underscores a growing and underappreciated risk: forgotten edge hardware is not merely a compliance gap but exploitable infrastructure.

Jun 23, 2026

ROCA: RSA Encryption Vulnerability | SecPod