eMudhra, Brotli, and the Long Tail of a Security Fix
中文摘要
Node.js更新修复了eMudhra与Brotli漏洞,但由于相关解码器广泛嵌入各类应用,开发者仍需面对庞大的后续排查与修复工作。
English Summary
Node.js released patches for eMudhra and Brotli vulnerabilities, but the wide integration of these decoders across various runtimes creates an extensive challenge for developers to secure all software.
How much software do you have to update to fix one vulnerability, let alone two far-reaching ones in the same week? Our corner of the internet was getting impatient waiting for Node’s eMudhra fix to drop. The certificate block had merged, and we were ready to update Node, rebuild, and move on. Then the October 21 release dropped, and we got Brotli too. That covered both problems in Node. But how much else used that same decoder? It was tucked into other applications and runtimes, and now we had more places to look. And eMudhra had its own version of the same problem. Your browser could reject the compromised certificates while a command-line tool on the same machine still trusted them. Which other programs accepted them? Which certificate stores were they using? Updating Node only covered part of it. eMudhra: a trust decision that traveled off the map # On October 17, a researcher showed they had recovered eight eMudhra intermediate CA private keys by signing a message with each one. Scott Helme later recovered them from the public certificates on his laptop in less than a second. The values included 4, 56, and 115. These were supposed to be 384-bit private keys, with roughly 3.94 …