Menu

Chrome Blocked 8 eMudhra CA Keys on Oct 17. A Node Release From Oct 14 Still Trusts Them.
📰

Chrome Blocked 8 eMudhra CA Keys on Oct 17. A Node Release From Oct 14 Still Trusts Them.

DEV Community: security·Posting Dude·14 days ago
#sJEUUlmm
#devtosecurity#devto#dev#node#certifi
Reading 0:00
15s threshold

On Saturday, October 17, at 18:05 UTC, a researcher reported to the Chrome Root Program that the private keys of eight eMudhra intermediate CA certificates could be recovered by anyone. The keys had been generated with weak randomness. With one of them you can sign a certificate for any domain, and clients that still trust that intermediate will accept it.

Chrome blocked the keys 100 minutes later with a CRLSet push. Firefox blocked them the same day. Microsoft followed on the 20th, Apple on the 22nd, and Chrome removed the root above them, emSign ECC Root CA - G3, from its root store on October 27.

That covers browsers. Your backend is not a browser. It calls Stripe, sends webhooks and talks to your email provider through Node, Python or Go, and a lot of those don't read CRLSets. They check against a list of roots that shipped with the runtime or the package.

So I tested it. Same Debian 13 box, with the patched system ca-certificates (20250419+deb13u1) installed.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.