Firecracker 微虚拟机逃逸漏洞
推荐指数 63.0 NO. 021 · 2026.11.07
发布2026/11/06Score119Comments61
简介
安全团队从 Firecracker 微虚拟机内部突破隔离，获取宿主机 root 权限。这是云原生沙箱的底层安全威胁，直接影响 Serverless 和容器服务的基础设施信任假设。
编辑判断
这个漏洞的杀伤链设计非常精巧：不是从外部攻破，而是利用 guest 对 host 内存的读写能力，直接篡改 Firecracker 进程的寄存器状态，让宿主线程"自愿"执行攻击者指定的代码。更值得警惕的是逃逸后 VM 仍保持 SSH 可达，隐蔽性极高。
AWS Lambda、Fargate 等基于 Firecracker 的服务需要紧急评估补丁状态。如果你在做多租户 Serverless 平台或基于 Firecracker 的私有云，这个攻击面意味着"guest 代码不可信"的假设已经不够，需要考虑额外的内核级隔离或监控层。安全团队建议关注官方后续补丁，同时审查现有实例的 KVM 版本和 Firecracker 配置。
社区反馈
意见分歧 45 条评论
核心争论：微内核形式化验证方案（Nova/L4）能否替代Linux生态成为更安全的虚拟化底座
I am more convinced by the day that the Nova Microhypervisor approach is correct. Do virtualization with a tiny formally verified microkernel and have complex kernels like Linux run underneath instead of letting a huge, complex, and brittle linux kernel and vm ecosystem control the hypervisor layer.
> the Nova Microhypevisor approach is correct To save people the time: "This code is experimental and not feature complete. If it breaks, you get to keep both pieces."
The actual main open source repo has had that warning there for 14 years in spite of commercial forks that are deployed in production government and high risk use cases. See his latest talk which represents a lot of impressive recent work: https://cfp.3mdeb.com/media/bsmconf/