vuln-audit
Skill11 starsChanged 49 days agoMITView on GitHub
按清单系统性排查二进制漏洞模式（vulnerability audit / pwn 预筛）：内存破坏、格式化字符串、整数溢出、命令注入、危险 API 组合。触发：漏洞审计、找漏洞、pwn 攻击面梳理、fuzz 前目标筛选、SRC 静态预筛。是 checklist 知识层——具体命令见 ghidra-core。动手前必须先用 skill 工具加载本 skill 全文并遵守其流程；一切观察/结论用 ledger.py 落账。
2 other projects use a version of this.
Adopted by
Most recently taken up by
- AL-JANEF/janef-forgetheir own version, first seen Sep 19, 2026
- AL-JANEF/janefskillstheir own version, first seen Sep 19, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- AL-JANEF/janef-forge★ 1same name
- AL-JANEF/janefskills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- android-reSkill
- ghidra-coreSkill
- ghidra-staticSkill
- pwn-exploitSkill
- re-dynamicSkill
- re-triageSkill
- re-unpackSkill
- traffic-analysisSkill
The file
Files
Vuln Audit（场景 3：它有没有病？）
前置：未知样本先分诊 → ~/.dsh/skills/re-triage／后继：命中漏洞模式后的利用构造（pwn 方法论，超出本 skill）／执行细节（命令参数）→ ~/.dsh/skills/ghidra-core
本 skill 是 checklist 知识层：方法论和判定标准在这里，命令只有用法示意，参数细节一律见 ghidra-core §5。
路径约定
SK="$HOME/.dsh/skills/ghidra-core/scripts" # 唯一代码家
# Windows:
RPC="$HOME/Desktop/src/ghidra-bridge/ghidra-rpc-venv/Scripts" # ghidra-rpc CLI
# WSL/Linux: RPC="$HOME/ghidra-rpc-venv/bin"审计流程
python "$SK/rpc_driver.py" ensure <bin>+triage：拿到 imports 全貌与可疑 API 六组命中——这是第一轮粗筛- 按
references/vuln-patterns.md的检查项清单逐项过：每项给出识别信号、用什么命令查、判定标准、常见误报 - 每个命中项记录：地址 / 证据（伪码或汇编摘录）/ 可达性（用户输入能否到达）/ 严重度初判
- 可达性优先于模式数量：一个用户输入直达的 strcpy 胜过十个内部路径的 gets。用
xrefs-to确认调用者、用decompile追输入来源（main 参数/recv/read/文件/环境变量） - 交付：命中清单 + 每项证据 + 建议的 fuzz/动态验证入口（动态工具是否已装以
python "$SK/doctor.py"的 toolchain 节为准，未装的按 hint 装或改静态验证）
覆盖的检查项（细则在 references/vuln-patterns.md）
- 栈溢出（gets/strcpy/sprintf/strcat vs 边界检查版）
- 格式化字符串（printf(用户输入)）
- 堆问题（UAF / double-free 的 free 后指针未清零模式）
- 整数溢出（malloc 前算术）
- 命令注入（system/popen/ShellExecute 拼用户输入）
- 危险 API 组合（对应 triage 可疑六组）
- 不安全的随机数（rand/srand(time) 作安全用途）
- 硬编码密钥/口令特征
与其他 skill 的分水岭
- vs re-triage：分诊回答"这是什么、走哪条路"，本 skill 回答"按清单查有没有这些病"。判型/壳/语言问题去 re-triage
- vs ghidra-static：static 是"读懂它"（语义还原、算法提取），本 skill 是"挑毛病"（模式匹配+可达性）。深挖某个函数的实现细节去 ghidra-static
References
| 文件 | 何时读 |
references/vuln-patterns.md | 漏洞模式检查项清单（识别信号/命令/判定标准/误报）——审计主文档 |
references/patch-diff.md | 有补丁前后两版二进制时：ghidriff/version-track 差分 → 根因反推 → PoC 思路（N-day） |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.