用大模型+形式化方法自动发现修复容器逃逸漏洞。
Bulkhead: Automated Semantic Detection and Remediation of Container Escape Vulnerabilities

- 结合大模型与形式化方法,通过多维度模式识别漏洞入口。
- 可定位跨边界交互中的路径遍历漏洞并生成验证性攻击代码。
- 适合云原生安全团队和AI系统开发者使用。
容器生态中的文件系统隔离常因跨边界路径误解析而被削弱,导致路径遍历(PaTra)漏洞。此类漏洞源于不安全的主机-容器交互,在云系统将GPU、代理工作区等共享资源注入容器以支持AI负载的背景下日益普遍。现有防御手段不足:内核级防护侵入性强,易破坏系统调用,未被纳入Linux主线;检测方法依赖静态规则匹配或人工审计,规则无法捕捉语义信息,导致大量误报;人工审查需领域知识,成本高、效率低且难扩展。为此,我们提出Bulkhead——一个融合大语言模型(LLMs)与形式化方法的自动化框架,用于语义漏洞发现与修复。Bulkhead采用多智能体系统,基于已知案例的多维知识模式,首先通过高风险函数模式定位容器化代码中跨边界交互的入口点,再利用调用链模式恢复对应执行路径至合适深度。检测流水线分析这些调用链与应用场景及威胁模型,识别出缺失安全检查、TOCTOU缺陷等跨边界交互漏洞,并生成验证用的漏洞利用原型(PoC)。这些PoCs进一步指导补丁生成。为确保修复正确性,修复流水线采用预设的模型检验模板进行断言驱动验证。
原文摘要 · Abstract (English)
Filesystem isolation in container ecosystems is often weakened by cross-boundary path misresolution, causing path traversal (PaTra) vulnerabilities. These vulnerabilities stem from insecure host-container interactions and have become increasingly pervasive as cloud systems mount shared resources, such as GPUs and agent workspaces, into containers to support AI workloads. Existing defenses remain inadequate. Kernel-level protections are intrusive, can destabilize system calls, and have therefore not been accepted into the Linux mainline. Detection methods rely on static rule matching or manual code auditing. Static rules can flag path-related functions but fail to capture the semantics needed to determine whether a host-container interaction exists, causing many false positives. Manual review requires domain expertise, making it costly, inefficient, and difficult to scale. To address this threat, we present Bulkhead, an automated framework that integrates large language models (LLMs) with formal methods for semantic vulnerability discovery and remediation. Bulkhead uses a multi-agent system to identify and repair PaTra vulnerabilities through multi-dimensional knowledge patterns generalized from known cases. It first applies high-risk functional patterns to locate entry points for cross-boundary interactions in containerized code, then uses call-chain patterns to recover the corresponding execution paths at suitable depth. The Detection pipeline analyzes these call chains against the application scenarios and threat model, identifying vulnerabilities such as missing security checks and TOCTOU flaws in cross-boundary interactions, and generating proof-of-concept (PoC) exploits for validation. These PoCs then guide patch generation. To ensure remediation correctness, the Patch pipeline performs assertion-driven verification using predefined model-checking templates.
Thank you to arXiv for use of its open access interoperability. PaperDance 不是 arXiv 官方产品;中文卡片由大模型生成,请以原文为准。