Tuesday 3 November
Global

Your region, kept on this device.

Cloudflare tracks exploitation and patching of eMudhra's weak intermediate CA keys

Severity
High
Sources
1

's eight weak intermediate keys (values 4, 56, 66, 115, 155, 156, 230 and 237) are recoverable from public certificates, so any client that trusts them and does not enforce Certificate Transparency will accept forged certificates for any domain. patched Pingora to reject them and added logging by October 21. It saw about 22,000 handshakes, two-thirds to test sites, with all verifying handshakes refused. About 160 presented certificates naming unrelated SANs, some valid for over two years; these looked like server default certificates and would have failed hostname verification. Defenders should remove or distrust the eMudhra intermediates, enforce Certificate Transparency, and watch for certificates chained to these keys. eMudhra says a key generation script mistake was responsible but has not shared the script.

For security analysts · Written by AI from 1 source · Wrong?

What to do

  1. Check whether you use the affected product, and install the vendor’s fix when it is available. Open your watchlist

General advice for this kind of story

Full story timeline · 1 update

  1. Fri 30 October4 real? Tracking exploitation and patching of eMudhra’s weak keysCloudflare Blog (Security)

Who reported · 1 outlet

Cloudflare Blog (Security)

Who and what is in it

Report a problem