ROCA vulnerability
| CVE identifier(s) | CVE-2017-15361 |
|---|---|
| Date discovered | February 2017 |
| Discoverer | Matúš Nemec, Marek Sýs, et al. (Masaryk University) |
| Affected hardware | TPM, Yubikey, Gemalto IDPrime .NET smart cards |
| Affected software | Any public-private key encryption that used RSALib including BitLocker and PGP |
The ROCA vulnerability is a cryptographic weakness that allows the private key of a key pair to be recovered from the public key in keys generated by devices with the vulnerability. "ROCA" is an acronym for "Return of Coppersmith's attack".[1] The vulnerability has been given the identifier CVE-2017-15361.
The vulnerability arises from a problem with an approach to RSA key generation used in vulnerable versions of a software library, RSALib, provided by Infineon Technologies, and incorporated into many smart cards, Trusted Platform Module (TPM), and Hardware Security Modules (HSM) implementations, including YubiKey 4 tokens, often used to generate PGP keys. Keys of lengths 512, 1024, and 2048 bits generated using these versions of the Infineon library are vulnerable to a practical ROCA attack.[2][3] The research team that discovered the attack (all with Masaryk University and led by Matúš Nemec and Marek Sýs)[2] estimate that it affected around one-quarter of all current TPM devices globally.[4] Millions of smart cards are believed to be affected.[1]
The team informed Infineon of the RSALib problem in February 2017, but withheld public notice until mid-October, citing responsible disclosure. At that time they announced the attack and provided a tool to test public keys for vulnerability. They published the details of the attack in November.[2]
Technical details
Generating an RSA key involves selecting two large randomly-generated prime numbers, a process that can be time-consuming, particularly on small devices, such as smart cards. In addition to being primes, the numbers should have certain other properties for best security. The vulnerable RSALib selection process quickly creates primes of the desired type by only testing for primality numbers of the form:
- [math]\displaystyle{ k * M + (65537^a \mod{M}) }[/math]
where [math]\displaystyle{ M }[/math] is the product of the first n successive primes (2, 3, 5, 7, 11, 13,...), and n is a constant that only depends on the desired key size. The security is based on the secret constants [math]\displaystyle{ k }[/math] and [math]\displaystyle{ a }[/math]. The ROCA attack exploits this particular format for primes using a variation of the Coppersmith method. In addition, public keys generated this way have a distinctive fingerprint that can be quickly recognized by attempting to compute the discrete logarithm of the public key mod [math]\displaystyle{ M }[/math] to base 65537. Computing discrete logarithms in a large group is usually extremely difficult, but in this case it can be done efficiently using the Pohlig–Hellman algorithm because [math]\displaystyle{ M }[/math] is a smooth number. A test site is available on the Internet.[2][5][6][7] In short, keys that fit this format have significantly low entropy and can be attacked relatively efficiently (weeks to months), and the format can be confirmed ("fingerprinted") by the attacker very quickly (microseconds). Multiple implementations of the attack are publicly available.[8][9][10]
Mitigation
The ROCA authors consider public keys of length 512, 1024 and 2048-bits generated by RSALib to be vulnerable. Because the details of key generation differ for different key lengths, shorter keys are not necessarily more vulnerable than longer keys. For example, a 1952-bit RSAlib key is stronger than a 2048-bit key and a 4096-bit key is weaker than a 3072-bit key.
The best mitigation, according to the authors, is to generate RSA keys using a stronger method, such as by OpenSSL. If that is not possible, the ROCA authors suggest using key lengths that are less susceptible to ROCA such as 3936-bit, 3072-bit or, if there is a 2048-bit key size maximum, 1952-bits.[2]:Sec 5.1
Infineon has released firmware updates for its Trusted Platform Modules to manufacturers who have used its TPMs.[11]
Implications
The vulnerability highlighted several shortcomings of the Common Criteria certification scheme as the vulnerability was present in a list of Common Criteria certified smart card products. Namely, the approval of homegrown cryptographic algorithms; the lack of transparency in certification reports, inability to revoke Common Criteria certificates for known vulnerable products and distribute this information to the users of the certified products.[12]:Sec 6.7.5
In Estonia, the discovery of the vulnerability resulted in a state-level cyber crisis as the vulnerable smart card chip was deployed on more than 750,000 Estonian identity cards that are used daily by Estonian residents and e-residents to securely authenticate online and create digital signatures.[12]:Sec 6.7
See also
References
- ↑ 1.0 1.1 Goodin, Dan (2017-10-23). "Crippling crypto weakness opens millions of smartcards to cloning" (in en-us). Ars Technica. https://arstechnica.com/information-technology/2017/10/crippling-crypto-weakness-opens-millions-of-smartcards-to-cloning/.
- ↑ 2.0 2.1 2.2 2.3 2.4 Nemec, Matus; Sys, Marek; Svenda, Petr; Klinec, Dusan; Matyas, Vashek (November 2017). "The Return of Coppersmith's Attack: Practical Factorization of Widely Used RSA Moduli". doi:10.1145/3133956.3133969. https://crocs.fi.muni.cz/_media/public/papers/nemec_roca_ccs17_preprint.pdf.
- ↑ Khandelwal, Swati. "Serious Crypto-Flaw Lets Hackers Recover Private RSA Keys Used in Billions of Devices". The Hacker News. https://thehackernews.com/2017/10/rsa-encryption-keys.html.
- ↑ Leyden, John (16 October 2017). "Never mind the WPA2 drama... Details emerge of TPM key cockup that hits tonnes of devices". United Kingdom: The Register. https://www.theregister.co.uk/2017/10/16/roca_crypto_vuln_infineon_chips/.
- ↑ "ROCA: Infineon TPM and Secure Element RSA Vulnerability Guidance". United Kingdom. https://www.ncsc.gov.uk/guidance/roca-infineon-tpm-and-secure-element-rsa-vulnerability-guidance.
- ↑ "ROCA: Vulnerable RSA generation (CVE-2017-15361)". Czech Republic: Centre for Research on Cryptography and Security, Faculty of Informatics, Masaryk University. https://crocs.fi.muni.cz/public/papers/rsa_ccs17.
- ↑ "Information on software update of RSA key generation function". Infineon Technologies AG. https://www.infineon.com/cms/en/product/promopages/rsa-update/.
- ↑ Bruno Produit (2019-05-15). "Implementation of the ROCA attack (CVE-2017-15361)". https://github.com/brunoproduit/roca.
- ↑ Florian Picca (2020-05-03). "ROCA". https://github.com/FlorianPicca/ROCA.
- ↑ Shiho Midorikawa (2020-04-13). "ROCA". https://github.com/elliptic-shiho/crypto_misc/blob/master/small_root/roca_attack.sage.
- ↑ ""TPM Update - Infineon Technologies"". https://www.infineon.com/cms/en/product/promopages/tpm-update/.
- ↑ 12.0 12.1 Parsovs, Arnis (March 2021). Estonian Electronic Identity Card and its Security Challenges (PhD). University of Tartu.
External links
- ROCA detection tool (Detection source code)
- ROCA Vulnerability Test Suite (Online tool for testing keys, files, GitHub accounts, GnuPG keys, and includes an S/MIME and PGP email responder)
- TrustMonitor ROCA Vulnerability Test (Online tool for testing multiple certificates)
- Detect Trusted Platform Modules Vulnerable to CVE-2017-15361 (Scripts)
 |  |
