r/cybersecurity: eight eMudhra TLS certificates found with private keys only a few bits long
Why a single weak certificate authority can matter to everyone, and the long cleanup ahead.
The post links Ars Technica's report that eight intermediate TLS certificates belonging to the India-based certificate authority eMudhra had private keys of only 3 to 8 bits (a normal P-384 key has about 384 bits), so anyone could use them to issue certificates that browsers and apps would trust for any site. Ars says browser makers and some major apps and programming languages had blocked all eight by Tuesday, with no sign yet of malicious use in certificate transparency logs, but cryptography engineer Filippo Valsorda called it "a massive cleanup job, bigger than Heartbleed," because of Linux distributions, containers and IoT devices. Exploiting it requires intercepting traffic.
Replies from defenders range from gallows humor about ruined evenings to disbelief at the key sizes. Others question why systems automatically trust so many certificate authorities, and note that the certificates had been cross-signed by Sectigo. About 3,100 upvotes in a 1.1-million-member community.
-
Certificate authority
After exploring The Internet goes on high alert after discovery of 8 compromised TLS certs, the trust system behind it is explained in Certificate authority.
Wikipedia explains certificate authorities: the trusted third parties that sign and issue the digital certificates proving who owns a public key.
Wikipedia · Wade · 5 min
0 -
Heartbleed
After exploring The Internet goes on high alert after discovery of 8 compromised TLS certs, for the benchmark everyone is citing, see Heartbleed.
The OpenSSL bug introduced in 2012 and disclosed in April 2014, a buffer over-read in a widely used TLS library, which experts compared this cleanup to.
Wikipedia · Wade · 5 min
0