Back to Details

offensive-exploit-development

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Memory Corruption Root-Cause Analysis (
offensive-exploit-development
)

内存损坏根因分析 (
offensive-exploit-development
)

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

概述

Memory corruption root-cause analysis and patch engineering covering stack and heap buffer overflows, use-after-free (UAF), type confusion, integer overflow calculations, and compiler sanitizer verification.
内存损坏根因分析与补丁工程，涵盖栈和堆缓冲区溢出、释放后使用（UAF）、类型混淆、整数溢出计算以及编译器 Sanitizer 验证。

Operational Workflow

操作工作流

  1. Surface & Architecture Inventory
    • Identify all entrypoints, trust boundaries, parsers, and configuration files relevant to Memory Corruption Root-Cause Analysis (
      exploit-dev
      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. 攻击面与架构清单
    • 识别与内存损坏根因分析（
      exploit-dev
      领域）相关的所有入口点、信任边界、解析器和配置文件。
    • 将静态代码/二进制检查（通过 REA MCP 工具、
      rg
      、AST 分析或反编译）与运行时配置验证相结合。
  2. 假设与漏洞验证
    • 根据已知 CWE 和 OWASP 模式，系统地测试每项安全不变量。
    • 记录具体证据：受影响的文件/过程、行号或二进制偏移量、请求/响应跟踪以及根因。
  3. 影响与可达性分诊
    • 评估问题是否可跨信任边界触达、纵深防御控制是否能够缓解问题，并计算准确的 CVSS v3.1 / v4.0 分数。
  4. 修复与回归验证
    • 实施或提供达到生产就绪标准、可直接复制粘贴的修复代码。
    • 编写自动化回归测试或验证命令，证明缺陷已解决且存在 0 个回归问题。

Audit & Verification Checklist

审计与验证清单

PhaseCheckVerification MethodExpected Secure State
1. DiscoveryEnumerate all 
exploit-dev
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. 发现枚举所有 
exploit-dev
攻击面和依赖项		源代码搜索 / REA 二进制与包检查完整梳理信任边界
2. 输入与状态验证解析器行为、类型安全性和状态转换边界测试与静态污点分析严格的 Schema 验证和不变量检查
3. 身份验证与隔离验证调用方身份、租户隔离和最小权限原则水平/垂直权限矩阵检查显式执行默认拒绝策略
4. 纵深防御检查次级控制措施、日志记录以及编译器/运行时标志配置与头文件/二进制标志审计全面启用强化配置和遥测
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 向量、CWE 映射和修复补丁来格式化发现的问题。