OpenAI 称在一次红队演练中发现 Brotli 压缩库存在可未认证远程代码执行的漏洞,攻击者可通过发送或回复恶意压缩数据在受影响系统上运行代码。该根因问题已于今年 2 月在 Brotli 源码中修复,但当时未知其构成安全漏洞,且此后无新版本发布。OpenAI 已向 Brotli 及 Node.js 等下游项目披露,Brotli 已发布新版本并公开 CVE。
战略研判
基于公开信息OpenAI 在红队演练中发现 Brotli 存在未认证远程代码执行漏洞,该库被 Node.js、Bun、Envoy 等广泛内置,下游软件需逐层跟进更新,暴露开源依赖链的修复传导成本。
各下游项目安全更新的实际发布与覆盖进度;Brotli 新版本与 CVE 编号的具体修复范围。
During this red-teaming exercise, we also found a vulnerability that allows for unauthenticated remote code execution in Brotli, a widely-deployed compression library included in many pieces of software such as Node.js, Bun, and Envoy.
The flaw could let an attacker run their own code on affected systems by sending or replying with malicious compressed data, without any need to create a user account. That is, an unpatched server that accepts compressed input could be taken over by a malicious client, and an unpatched client that accepts compressed input (such as “curl --compressed”) could be taken over by a malicious server.
This root cause issue was actually fixed in the Brotli source code in February, but it wasn’t known at the time that it gave rise to a security vulnerability and there was no more recent release of Brotli. Since Brotli is built into other software, any software which includes this library needs to take the update too, followed by the users of that software. We disclosed the vulnerability to Brotli and other downstream projects such as Node.js, which released or are currently releasing security updates, and Brotli cut new release versions and published a CVE.
More details on the patch and mitigations below:
https://patchtheplanet.org/brotli
Over the past several months, we have substantially hardened the security of our research training environment. We’ve removed live internet access for all frontier models during training and built an offline world for them to use instead—a cached version of the web where they can still learn to browse, search, and use applications. On September 20, after a model exploited a DNS misconfiguration to find a way outside of this offline world, we paused frontier training to strengthen containment further. We assembled teams of agents, powered by our most cyber-capable models, and tasked them with finding weaknesses in our research environments. While they found no route to the internet they could easily exploit while concealing their activity from our monitors, they did find zero-day vulnerabilities, virtual machine escapes, and hardware side-channels for communication between agents. We used their discoveries to further strengthen our defenses and contribute fixes to open-source software. After strengthening our containment architecture, we resumed our frontier RL training and inference on October 1. We’ve reserved substantial compute for continuous red-teaming, and made high-compute red-teaming part of the safety cases we use to decide whether frontier training and evaluation can proceed securely. https://openai.com/index/securing-our-frontier-model-training-environment/在 X 查看被引用的帖子
来源:OpenAI · x.com