{ "version": 1, "event_id": "evt_b556f6f05750ec0d", "url": "https://xiyu.news/events/evt_b556f6f05750ec0d/", "json": "https://xiyu.news/api/events/evt_b556f6f05750ec0d.json", "type": "security_incident", "status": "developing", "category": "technology", "title": { "zh": "EMudhra 中间 CA 遭入侵", "en": "EMudhra Intermediate CA Compromise" }, "current_state": { "zh": "8 个受影响的 eMudhra 中间 CA 已被主要浏览器、Cloudflare 及多个开发语言/框架生态紧急封堵，eMudhra 也已正式吊销相关证书；尚未发现脆弱私钥被用于签发伪造证书的证据，但物联网设备和未更新旧系统仍存在清理与暴露风险。", "en": "The eight affected eMudhra intermediate CAs have been emergency-blocked by major browsers, Cloudflare, and several developer language/framework ecosystems, and eMudhra has formally revoked the certificates; no evidence yet shows the weak keys were used to forge certificates, but IoT devices and unpatched legacy systems remain exposed and cleanup is ongoing." }, "first_seen_at": "2026-10-20T17:25:49.327432+00:00", "last_updated_at": "2026-10-21T09:29:57.659443+00:00", "last_material_change_at": "2026-10-21T09:29:57.659443+00:00", "confidence": 0.75, "updates_count": 3, "sources_count": 3, "entities": [ "compromise", "emudhra", "intermediate", "tech" ], "identifiers": [], "topics": [ "browser-security", "certificate-authority", "cybersecurity", "emudhra", "mitm", "pki", "revocation", "security-incident", "tls", "tls-certificates" ], "updates": [ { "update_id": "upd_71042630278475ca", "event_id": "evt_b556f6f05750ec0d", "occurred_at": "2026-10-20T13:58:33Z", "published_at": "2026-10-20T13:58:33Z", "first_seen_at": "2026-10-20T17:25:49.327432Z", "time_precision": "published", "update_type": "initial", "material_change": true, "title_zh": "eMudhra 中间证书颁发机构被攻陷", "title_en": "EMudhra Intermediate CA Compromise", "what_changed_zh": "eMudhra 的中间 ECC 证书颁发机构被发现私钥实际上可被猜测——据报道只有一个字节（其中一个私钥字面值就是“4”），根源在于某一天用于生成这些 ECC 签发者的 KGC 脚本存在缺陷。浏览器厂商随即撤销了对相关中间 CA 的信任，而未采用现代吊销机制的非浏览器 TLS 客户端仍暴露在风险之中。\n\n由于这些中间 CA 属于公开受信任的机构，任何能猜出私钥的人都可以为任意域名伪造证书，而这种风险在生态中的分布极不均衡。一位 Mozilla 工程师表示，Firefox 用户通过 OneCRL 在两小时内即自动获得保护，Chrome、Apple 和 Microsoft 也有类似机制，但“生态中的其余部分在吊销机制上几乎没有任何投入”。\n\n在 Mozilla 缺陷报告 2083449 中，eMudhra 表示初步评估发现“当天用于创建这些 ECC 签发者的 KGC 脚本存在缺陷”，并称对 KGC 代码和 HSM 密钥的审查迄今显示：一组原始 ECC 密钥按预期在硬件内生成，此外还存在一项对其常规 KGC 流程的获批偏离。社区讨论提到共有 8 个受影响的 CA，一位评论者称这些密钥据称是在某个公开仓库 URL 上被发现的，同时表示不确定这些文件说明的是密钥被窃取，还是密钥生成过程本身过弱。", "what_changed_en": "eMudhra's intermediate CA private keys turned out to be single-byte values, enabling trivial forgery of certificates chaining to a trusted root until browsers revoked the CAs within hours.", "current_state_zh": "eMudhra 的中间 ECC 证书颁发机构被发现私钥实际上可被猜测——据报道只有一个字节（其中一个私钥字面值就是“4”），根源在于某一天用于生成这些 ECC 签发者的 KGC 脚本存在缺陷。浏览器厂商随即撤销了对相关中间 CA 的信任，而未采用现代吊销机制的非浏览器 TLS 客户端仍暴露在风险之中。\n\n由于这些中间 CA 属于公开受信任的机构，任何能猜出私钥的人都可以为任意域名伪造证书，而这种风险在生态中的分布极不均衡。一位 Mozilla 工程师表示，Firefox 用户通过 OneCRL 在两小时内即自动获得保护，Chrome、Apple 和 Microsoft 也有类似机制，但“生态中的其余部分在吊销机制上几乎没有任何投入”。\n\n在 Mozilla 缺陷报告 2083449 中，eMudhra 表示初步评估发现“当天用于创建这些 ECC 签发者的 KGC 脚本存在缺陷”，并称对 KGC 代码和 HSM 密钥的审查迄今显示：一组原始 ECC 密钥按预期在硬件内生成，此外还存在一项对其常规 KGC 流程的获批偏离。社区讨论提到共有 8 个受影响的 CA，一位评论者称这些密钥据称是在某个公开仓库 URL 上被发现的，同时表示不确定这些文件说明的是密钥被窃取，还是密钥生成过程本身过弱。", "current_state_en": "eMudhra's intermediate CA private keys turned out to be single-byte values, enabling trivial forgery of certificates chaining to a trusted root until browsers revoked the CAs within hours.", "detailed_summary_zh": "eMudhra's intermediate CA private keys turned out to be single-byte values, enabling trivial forgery of certificates chaining to a trusted root until browsers revoked the CAs within hours.", "detailed_summary_en": "eMudhra's intermediate CA private keys turned out to be single-byte values, enabling trivial forgery of certificates chaining to a trusted root until browsers revoked the CAs within hours.", "background_zh": "中间 CA 是代表根 CA 签发证书的委派签名层；攻陷其中一个，可以让运营方吊销该中间 CA 而不影响根 CA 或其他同级中间 CA。吊销一直是 TLS 的薄弱环节：浏览器通过 CRL 或 OCSP 检查状态，Mozilla 还叠加了面向中间证书的 OneCRL 和面向叶子证书的 CRLite，但许多 TLS 库和嵌入式客户端几乎不做此类检查。", "background_en": "Intermediate CAs are delegated signing layers that issue certificates on behalf of a root CA; compromising one lets the operator revoke that intermediate without invalidating the root or sibling intermediates. Revocation has long been the weak point of TLS: browsers check CRLs or OCSP, and Mozilla has layered on OneCRL for intermediates and CRLite for leaf certificates, but many TLS libraries and embedded clients perform little or no such checking.", "community_discussion_zh": "评论者对单字节密钥材料表示难以置信和嘲讽，有人称自己给“被攻陷”加上引号，“因为这么称呼实在让人难受”。一位 Mozilla 工程师关于 OneCRL/CRLite 处置方式及整个生态吊销能力不均衡的说明获得了最多实质性关注，也有人呼吁由具备资质的人澄清这些密钥究竟是被泄露还是仅仅可被猜出。", "community_discussion_en": "Commenters reacted with disbelief and derision at the single-byte key material, with one noting they put \"compromised\" in quotes \"because I can't call it that without cringing.\" A Mozilla engineer's explanation of OneCRL/CRLite remediation and the uneven state of revocation across the ecosystem drew the most substantive attention, and others asked for a qualified account of whether the keys were leaked or merely guessable.", "market_impact_zh": "这一风险通过 TLS 信任链而非任何代币基本面传导：在非浏览器客户端上终结 TLS 的加密交易所、托管机构、钱包后端和节点 RPC 端点可能并不查询 OneCRL 或 CRLite，在相关中间 CA 被从这些信任库中移除之前，API 与 webhook 流量存在被拦截的窗口。面向浏览器的服务大体已被厂商侧的吊销机制覆盖，因此残余风险集中在服务器间通信以及嵌入式/物联网基础设施上。", "market_impact_en": "The exposure runs through TLS trust rather than through any token's fundamentals: crypto exchanges, custodians, wallet backends and node RPC endpoints that terminate TLS in non-browser clients may not consult OneCRL or CRLite, leaving a window for interception of API and webhook traffic until the affected intermediates are removed from those trust stores. Browser-facing services were largely covered by vendor-side revocation, so the residual risk concentrates in server-to-server and embedded/IoT infrastructure.", "importance_score": 8.0, "references": [ { "url": "https://news.ycombinator.com/item?id=50166579", "title": "Community discussion" }, { "url": "https://lwn.net/Articles/983719/", "title": "That's great... for browsers. What of other TLS users? [LWN.net]" }, { "url": "https://www.ssl.com/blogs/how-do-browsers-handle-revoked-ssl-tls-certificates/", "title": "How Do Browsers Handle Revoked SSL/TLS Certificates? - SSL.com" }, { "url": "https://securew2.com/blog/root-vs-intermediate-certificates", "title": "Root vs. Intermediate Certificate Authority: Key Differences" } ], "confidence": 0.75, "story_ids": [ "hackernews:story:50166579" ], "sources": [ { "url": "https://emudhra.we-have-a-problem.com/", "label": "galadran", "source_type": "hackernews", "official": false } ] }, { "update_id": "upd_85ad96623145a31f", "event_id": "evt_b556f6f05750ec0d", "occurred_at": "2026-10-21T05:15:00Z", "published_at": "2026-10-21T05:15:00Z", "first_seen_at": "2026-10-21T06:41:49.551817Z", "time_precision": "published", "update_type": "response", "material_change": true, "title_zh": "科技巨头紧急封禁 8 张 eMudhra 证书，因其可能被用于伪造网站", "title_en": "Tech giants rush to block 8 eMudhra certs that could enable fake sites", "what_changed_zh": "新增了更具体的响应进展：Mozilla 独立复现并确认私钥生成缺陷；Cloudflare 于周一获悉后于周二为 Cloudflare One、WARP 客户端和 Tunnel 发布更新及缓解措施；Chrome 自周六、Apple 设备自周一、Microsoft 平台自周二起已封堵相关证书；Firefox 还为自定义设置用户发布桌面和 Android 更新。报道同时称，主要浏览器未发现被利用证据，证书透明度日志自 2025 年 4 月以来没有这些中间 CA 的记录，但浏览器生态之外许多不强制 CT 的客户端仍面临风险。", "what_changed_en": "Added concrete response details: Mozilla independently recovered and confirmed the flawed keys; Cloudflare released updates for Cloudflare One, WARP Clients and Tunnel on Tuesday; Chrome blocked the certificates since Saturday, Apple since Monday, Microsoft since Tuesday; Firefox released Desktop and Android updates for users with custom settings. The report also says major browsers show no evidence of exploitation, certificate transparency logs have no entries for the intermediate CAs since April 2025, and non-browser clients that do not enforce CT remain at risk.", "current_state_zh": "eMudhra 的 8 个受影响中间 CA 已被主要浏览器和 Cloudflare 等厂商紧急封堵或缓解；主要浏览器暂无被利用证据，但不强制证书透明度的非浏览器客户端仍可能暴露于伪造证书风险。", "current_state_en": "The eight affected eMudhra intermediate CAs have been emergency-blocked or mitigated by major browsers and Cloudflare; major browsers show no evidence of exploitation, but non-browser clients that do not enforce Certificate Transparency may remain exposed to forged certificates.", "detailed_summary_zh": "Major technology companies deployed emergency blocks against eight vulnerable eMudhra intermediate certificates after a private-key generation flaw made them trivial to exploit for impersonating legitimate websites.", "detailed_summary_en": "Major technology companies deployed emergency blocks against eight vulnerable eMudhra intermediate certificates after a private-key generation flaw made them trivial to exploit for impersonating legitimate websites.", "background_zh": "", "background_en": "", "community_discussion_zh": "", "community_discussion_en": "", "market_impact_zh": "", "market_impact_en": "", "importance_score": 8.0, "references": [], "confidence": 0.97, "story_ids": [ "rss:cointelegraph.com_rss:a0df8e511dd44c50" ], "sources": [ { "url": "https://cointelegraph.com/news/tech-giants-rush-to-block-flawed-emudhra-certs-that-could-enable-fake-sites?utm_source=rss_feed&utm_medium=rss&utm_campaign=rss_partner_inbound", "label": "Cointelegraph", "source_type": "rss", "official": false } ] }, { "update_id": "upd_466d2041abd54d0a", "event_id": "evt_b556f6f05750ec0d", "occurred_at": "2026-10-21T06:47:02Z", "published_at": "2026-10-21T06:47:02Z", "first_seen_at": "2026-10-21T09:29:57.659443Z", "time_precision": "published", "update_type": "response", "material_change": true, "title_zh": "印度CA机构eMudhra曝私钥生成漏洞，全球浏览器紧急拉黑防范中间人攻击", "title_en": "印度CA机构eMudhra曝私钥生成漏洞，全球浏览器紧急拉黑防范中间人攻击", "what_changed_zh": "新增了 eMudhra 已正式吊销存在缺陷的证书，以及 Go、Python、Rust、Electron 等主流开发语言和框架已推送更新并在各自生态内封禁相关证书的响应细节。", "what_changed_en": "Added that eMudhra has formally revoked the defective certificates and that major developer ecosystems including Go, Python, Rust, and Electron have pushed updates to block the affected certificates within their own trust stores.", "current_state_zh": "8 个受影响的 eMudhra 中间 CA 已被主要浏览器、Cloudflare 及多个开发语言/框架生态紧急封堵，eMudhra 也已正式吊销相关证书；尚未发现脆弱私钥被用于签发伪造证书的证据，但物联网设备和未更新旧系统仍存在清理与暴露风险。", "current_state_en": "The eight affected eMudhra intermediate CAs have been emergency-blocked by major browsers, Cloudflare, and several developer language/framework ecosystems, and eMudhra has formally revoked the certificates; no evidence yet shows the weak keys were used to forge certificates, but IoT devices and unpatched legacy systems remain exposed and cleanup is ongoing.", "detailed_summary_zh": "Indian CA eMudhra exposed eight intermediate certificates with trivially crackable private keys, prompting global browsers and developer ecosystems to blacklist them and update trust stores to prevent HTTPS man-in-the-middle attacks.", "detailed_summary_en": "Indian CA eMudhra exposed eight intermediate certificates with trivially crackable private keys, prompting global browsers and developer ecosystems to blacklist them and update trust stores to prevent HTTPS man-in-the-middle attacks.", "background_zh": "", "background_en": "", "community_discussion_zh": "", "community_discussion_en": "", "market_impact_zh": "", "market_impact_en": "", "importance_score": 8.0, "references": [], "confidence": 0.94, "story_ids": [ "telegram:theblockbeats:201591" ], "sources": [ { "url": "https://m.theblockbeats.info/flash/372933?from=telegram", "label": "theblockbeats", "source_type": "telegram", "official": false } ] } ] }