Slashdot Mirror


Millions of High-Security Crypto Keys Crippled by Newly Discovered Flaw (arstechnica.com)

Slovak and Czech researchers have found a vulnerability that leaves government and corporate encryption cards vulnerable to hackers to impersonate key owners, inject malicious code into digitally signed software, and decrypt sensitive data, reports ArsTechnica. From the report: The weakness allows attackers to calculate the private portion of any vulnerable key using nothing more than the corresponding public portion. Hackers can then use the private key to impersonate key owners, decrypt sensitive data, sneak malicious code into digitally signed software, and bypass protections that prevent accessing or tampering with stolen PCs. The five-year-old flaw is also troubling because it's located in code that complies with two internationally recognized security certification standards that are binding on many governments, contractors, and companies around the world. The code library was developed by German chipmaker Infineon and has been generating weak keys since 2012 at the latest. The flaw is the one Estonia's government obliquely referred to last month when it warned that 750,000 digital IDs issued since 2014 were vulnerable to attack. Estonian officials said they were closing the ID card public key database to prevent abuse. On Monday, officials posted this update. Last week, Microsoft, Google, and Infineon all warned how the weakness can impair the protections built into TPM products that ironically enough are designed to give an additional measure of security to high-targeted individuals and organizations.

3 of 55 comments (clear)

  1. Time for a Key Audit by Anonymous Coward · · Score: 2, Informative

    If you use a Yubikey or other smart card for key generation, revoke them and generate new keys using OpenSSL. Any system relying on TPM 1.4 is also suspect. This flaw affects keys generated using Infineon smartcards. Currently 1024 bit keys are trivially broken and 2048 bit keys are broken but could cost tens of thousands of dollars in compute to crack. 3072 and 4096 bit keys are still quite safe but if regeneration is practical then you should still do it. The attack could always improve and reach them.

    1. Re:Time for a Key Audit by Allasard · · Score: 3, Informative

      Here is Yubico's statement on what features of the Yubikey 4 are affected:
      https://www.yubico.com/2017/10...

  2. Re:Specific details by JoshuaZ · · Score: 3, Informative

    Because I can't count apparently. The logic does go through with 3 digits as our example though so just pretend I said that.