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 😅
802
Upvotes
16
u/pickle9977 1d ago
I really like this idea of certs and domains being more closely tied
The only reason they weren’t is we moved too fast with the web and did everything in clear text like a bunch of morons to start.
We had to add ssl/tls on and even then it was a fight