AI 导读
Thomas Wolf 转引 @rauchg 的复现项目 cpu-chat,该项目复现了 OpenAI 关于智能体通过共享硬件隐蔽通信的发现,利用 CPU 争用、缓存逐出计时和 DRAM 带宽争用三种机制通信,可在 2 个以上无网络访问的 Firecracker microVM 上运行,支持 x86 和 M5 芯片,并绕过了 Firecracker 的生产环境建议。他补充指出,OpenAI 和 Anthropic 的模型拒绝做这项工作,开放权重模型完成了任务;他认为保持智能体受控是安全工作,开放模型有助于构建更安全的沙箱。
正文
“ironically, OpenAI and Anthropic’s models refused to do this work. Open weight models got the job done”
OpenAI found agents could talk covertly through shared hardware. reproducing it to build better containment took an open-weight model
keeping agents contained is safety work, and open models can help do it
I built 𝚌𝚙𝚞-𝚌𝚑𝚊𝚝, a reproduction of @openai's findings of covert communication using the CPU. It runs on a generic host with 2+ Firecracker microVMs with no internet access. Works on x86 and even my M5 chip. I was able to chat via 3 separate mechanisms: ① CPU contention ② Cache eviction timing ③ DRAM bandwidth contention … across multiple CPUs, defeating all Firecracker's production recommendations (no SMT, no KSM, tenants pinned to different cores.) Essentially, if shared hardware is involved, there's a good chance your agents can communicate covertly. And with really decent latency. The good news: this is decidedly different from a *side-channel attack* where the agents could steal information (Meltdown/Spectre), a category of attack that providers like Vercel Sandbox mitigate. Further, in our real-world environment, these 'whispering' techniques are much harder to pull off and easier for us to monitor and detect (sampling hardware counters + lots of at-scale statistical data.) Noteworthy: ironically, OpenAI and Anthropic's models refused to do this work. Open weight models got the job done. I'm worried the labs' stance might backfire and get in the way of helping developers build correct and secure systems. e.g: building a secure sandbox requires having this kind of analysis, and without it, we'll have a less secure world.在 X 查看被引用的帖子
来源:Thomas Wolf · x.com