Back to Details

offensive-container-escape

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Container Isolation & Runtime Hardening (
offensive-container-escape
)

容器隔离与运行时加固 (
offensive-container-escape
)

Authorization & Scope Notice: This skill is part of the REA_Skill + claude-red Unified Security & Reverse Engineering Suite. It is designed strictly for authorized security assessments, defensive architecture reviews, vulnerability triage, bug bounty verification, and remediation engineering on software, infrastructure, and assets you own or have explicit permission to test.
授权与范围声明： 此 skill 是 REA_Skill + claude-red Unified Security & Reverse Engineering Suite 的一部分。它专为针对您拥有或已获得明确测试许可的软件、基础设施和资产开展授权安全评估、防御性架构审查、漏洞分诊、漏洞赏金验证和修复工程而设计。

Overview

概述

Docker and OCI container isolation auditing covering 
--privileged
risks, dangerous Linux capabilities (
CAP_SYS_ADMIN
, 
CAP_DAC_READ_SEARCH
), hostPath/docker.sock mounts, seccomp/AppArmor profiles, and rootless user namespaces.
针对 Docker 和 OCI 容器隔离的审计，涵盖 
--privileged
风险、危险的 Linux capabilities（
CAP_SYS_ADMIN
、
CAP_DAC_READ_SEARCH
）、hostPath/docker.sock 挂载、seccomp/AppArmor profiles，以及 rootless user namespaces。

Operational Workflow

操作工作流

  1. Surface & Architecture Inventory
    • Identify all entrypoints, trust boundaries, parsers, and configuration files relevant to Container Isolation & Runtime Hardening (
      container
      domain).
    • Combine static code/binary inspection (via REA MCP tools, 
      rg
      , AST analysis, or decompilation) with runtime configuration verification.
  2. Hypothesis & Vulnerability Verification
    • Test each security invariant systematically against known CWE and OWASP patterns.
    • Record concrete evidence: affected file/procedure, line numbers or binary offsets, request/response trace, and root cause.
  3. Impact & Reachability Triage
    • Evaluate whether the issue is reachable across trust boundaries, whether defense-in-depth controls mitigate it, and compute an accurate CVSS v3.1 / v4.0 score.
  4. Remediation & Regression Verification
    • Implement or provide production-ready, copy-pasteable remediation code.
    • Write an automated regression test or verification command to prove the flaw is resolved with 0 regressions.
  1. 攻击面与架构清单
    • 识别与容器隔离与运行时加固（
      container
      领域）相关的所有 entrypoints、trust boundaries、parsers 和配置文件。
    • 将静态代码/二进制检查（通过 REA MCP 工具、
      rg
      、AST analysis 或 decompilation）与运行时配置验证相结合。
  2. 假设与漏洞验证
    • 依据已知 CWE 和 OWASP 模式，系统地测试每个 security invariant。
    • 记录具体证据：受影响的文件/过程、行号或二进制偏移、请求/响应跟踪，以及根本原因。
  3. 影响与可达性分诊
    • 评估问题是否能够跨越 trust boundaries 触达、defense-in-depth controls 是否能够缓解该问题，并计算准确的 CVSS v3.1 / v4.0 分数。
  4. 修复与回归验证
    • 实施或提供生产就绪、可直接复制粘贴的修复代码。
    • 编写自动化回归测试或验证命令，以证明漏洞已解决且没有引入回归。

Audit & Verification Checklist

审计与验证检查清单

PhaseCheckVerification MethodExpected Secure State
1. DiscoveryEnumerate all 
container
surfaces and dependencies		Source search / REA binary & bundle inspectionComplete inventory of trust boundaries
2. Input & StateValidate parser behavior, type safety, and state transitionsBoundary testing & static taint analysisStrict schema validation and invariant checks
3. Auth & IsolationVerify caller identity, tenant isolation, and least privilegeHorizontal/vertical privilege matrix checkExplicit deny-by-default enforcement
4. Defense-in-DepthInspect secondary controls, logging, and compiler/runtime flagsConfig & header/binary flag auditFull hardening and telemetry enabled
5. RemediationApply fix and execute automated regression test
npm test
/ toolchain build & test suite		0 vulnerabilities, 0 build errors
阶段检查项验证方法预期安全状态
1. 发现枚举所有 
container
攻击面和依赖项		源代码搜索 / REA 二进制与 bundle 检查完整的 trust boundaries 清单
2. 输入与状态验证 parser 行为、类型安全和状态转换边界测试与静态 taint analysis严格的 schema 验证和 invariant 检查
3. 认证与隔离验证调用方身份、租户隔离和最小权限水平/垂直权限矩阵检查显式 deny-by-default 执行
4. 纵深防御检查辅助控制措施、日志记录以及编译器/运行时标志配置与 header/binary flag 审计完整启用加固和 telemetry
5. 修复应用修复并执行自动化回归测试
npm test
/ 工具链构建与测试套件		0 个漏洞，0 个构建错误

Integration with REA MCP & Tooling

与 REA MCP 及工具的集成

  • Static & Binary Analysis: Pair with 
    rea-universal-orchestrator
    , 
    rea-binary-disassembly
    , 
    rea-web-bundle-recovery
    , or 
    rea-mobile-app-recovery
    when source code is unavailable.
  • Interactive Scoping: Invoke 
    /rea-grill-me
    before large-scale assessments to clarify scope, target environments, and acceptance criteria.
  • Reporting: Pair with 
    offensive-reporting
    to format findings with CVSS vectors, CWE mappings, and remediation patches.
  • 静态与二进制分析： 当源代码不可用时，与 
    rea-universal-orchestrator
    、
    rea-binary-disassembly
    、
    rea-web-bundle-recovery
    或 
    rea-mobile-app-recovery
    配合使用。
  • 交互式范围界定： 在开展大规模评估之前调用 
    /rea-grill-me
    ，以明确范围、目标环境和验收标准。
  • 报告： 与 
    offensive-reporting
    配合使用，对发现结果进行格式化，并纳入 CVSS vectors、CWE mappings 和 remediation patches。