Security Leaked SSL Intermediate Certificates: https connections cannot be trusted
curl https://q3k.google.com --resolve 'q3k.google.com:443:135.181.235.221'
<!DOCTYPE html>
<meta charset="utf-8">
<title>q3k.google.com</title>
<meta name="viewport" content="width=device-width, initial-scale=1" />
<link rel="shortcut icon" type="image/png" href="/favicon.png">
<style>
body {
font: courier, sans-serif;
font-size: 12px;
text-align: center;
margin-top: 100px;
}
</style>
<p>
<b>oh, this is bad</b>
</p>
Yeah, eight SSL Intermediate Certificates of eMudhra have been publicly leaked. All your servers https traffic can be broken right now. Browsers are fine as they have revoked the certificates but as you can see, curl and many other libraries still accept those.
No download can be trusted right now. Remember to not only patch your main systems but every docker container you run.
This is bad 😅
797
Upvotes
1
u/AtlanticPortal 18h ago
And the certificates that have been leaked are certificates used for signing other certificates which are given to developers and used to sign code.
We are talking about both. The issue with the leaked private keys is that they are directly impacting code signing. A malicious actor can use the leaked keys to gov himself a code signing certificate and sign his malware.
Are we clear now?