检查
- 作者仓库星标 0
- 作者更新于 2026年8月24日 23:09
- 作者仓库 skills
- 领域
- 通用
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @trailofbits · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 允许外网请求
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
第 0 步:理解主张和背景
在进行任何分析之前,请用自己的话重述该错误。如果您不能清楚地做到这一点,请要求用户进行澄清。一半的误报在这一步崩溃了——如果精确地重述,这种说法就没有连贯的意义。文档:确切的漏洞声明是什么? (例如,“当 `content_length` 超过 4096 时,`parse_header()` 中堆缓冲区溢出”)所谓的根本原因是什么? (例如,“第 142 行 `memcpy` 之前缺少边界检查”)
# False Positive Check
## When to Use
- "Is this bug real?" or "is this a true positive?"
- "Is this a false positive?" or "verify this finding"
- "Check if this vulnerability is exploitable"
- Any request to verify or validate a specific suspected bug
## When NOT to Use
- Finding or hunting for bugs ("find bugs", "security analysis", "audit code")
- General code review for style, performance, or maintainability
- Feature development, refactoring, or non-security tasks
- When the user explicitly asks for a quick scan without verification
## Rationalizations to Reject
If you catch yourself thinking any of these, STOP.
| Rationalization | Why It's Wrong | Required Action |
|---|---|---|
| "Rapid analysis of remaining bugs" | Every bug gets full verification | Return to task list, verify next bug through all phases |
| "This pattern looks dangerous, so it's a vulnerability" | Pattern recognition is not analysis | Complete data flow tracing before any conclusion |
| "Skipping full verification for efficiency" | No partial analysis allowed | Execute all steps per the chosen verification path |
| "The code looks unsafe, reporting without tracing data flow" | Unsafe-looking code may have upstream validation | Trace the complete path from source to sink |
| "Similar code was vulnerable elsewhere" | Each context has different validation, callers, and protections | Verify this specific instance independently |
| "This is clearly critical" | LLMs are biased toward seeing bugs and overrating severity | Complete devil's advocate review; prove it with evidence |
---
## Step 0: Understand the Claim and Context
Before any analysis, restate the bug in your own words. If you cannot do this clearly, ask the user for clarification. Half of false positives collapse at this step — the claim doesn't make coherent sense when restated precisely.
Document:
- **What is the exact vulnerability claim?** (e.g., "heap buffer overflow in `parse_header()` when `content_length` exceeds 4096")
- **What is the alleged root cause?** (e.g., "missing bounds check before `memcpy` at line 142")
- **What is the supposed trigger?** (e.g., "attacker sends HTTP request with oversized Content-Length header")
- **What is the claimed impact?** (e.g., "remote code execution via controlled heap corruption")
- **What is the threat model?** What privilege level does this code run at? Is it sandboxed? What can the attacker already do before triggering this bug? (e.g., "unauthenticated remote attacker vs privileged local user"; "runs inside Chrome renderer sandbox" vs "runs as root with no sandbox")
- **What is the bug class?** Classify the bug and consult [bug-class-verification.md]({baseDir}/references/bug-class-verification.md) for class-specific verification requirements that supplement the generic phases below.
- **Execution context**: When and how is this code path reached during normal execution?
- **Caller analysis**: What functions call this code and what input constraints do they impose?
- **Architectural context**: Is this part of a larger security system with multiple protection layers?
- **Historical context**: Any recent changes, known issues, or previous security reviews of this code area?
## Route: Standard vs Deep Verification
After Step 0, choose a verification path.
### Standard Verification
Use when ALL of these hold:
- Clear, specific vulnerability claim (not vague or ambiguous)
- Single component — no cross-component interaction in the bug path
- Well-understood bug class (buffer overflow, SQL injection, XSS, integer overflow, etc.)
- No concurrency or async involved in the trigger
- Straightforward data flow from source to sink
Follow [standard-verification.md]({baseDir}/references/standard-verification.md). No task tracking — work through the linear checklist sequentially, documenting findings inline.
### Deep Verification
Use when ANY of these hold:
- Ambiguous claim that could be interpreted multiple ways
- Cross-component bug path (data flows through 3+ modules or services)
- Race conditions, TOCTOU, or concurrency in the trigger mechanism
- Logic bugs without a clear spec to verify against
- Standard verification was inconclusive or escalated
- User explicitly requests full verification
Follow [deep-verification.md]({baseDir}/references/deep-verification.md). Track each phase as a task with explicit dependencies, and execute the phases using the plugin's analysis agents.
### Default
Start with standard. Standard verification has two built-in escalation checkpoints that route to deep when complexity exceeds the linear checklist.
## Batch Triage
When verifying multiple bugs at once:
1. Run Step 0 for all bugs first — restating each claim often collapses obvious false positives immediately
2. Route each bug independently (some may be standard, others deep)
3. Process all standard-routed bugs first, then deep-routed bugs
4. After all bugs are verified, check for **exploit chains** — findings that individually failed gate review may combine to form a viable attack
## Final Summary
After processing ALL suspected bugs, provide:
1. **Counts**: X TRUE POSITIVES, Y FALSE POSITIVES
2. **TRUE POSITIVE list**: Each with brief vulnerability description
3. **FALSE POSITIVE list**: Each with brief reason for rejection
## References
- [Standard Verification]({baseDir}/references/standard-verification.md) — Linear single-pass checklist for straightforward bugs
- [Deep Verification]({baseDir}/references/deep-verification.md) — Full task-based orchestration for complex bugs
- [Gate Reviews]({baseDir}/references/gate-reviews.md) — Six mandatory gates and verdict format
- [Bug-Class Verification]({baseDir}/references/bug-class-verification.md) — Class-specific verification requirements for memory corruption, logic bugs, race conditions, integer issues, crypto, injection, info disclosure, DoS, and deserialization
- [False Positive Patterns]({baseDir}/references/false-positive-patterns.md) — 13-item checklist and red flags for common false positive patterns
- [Evidence Templates]({baseDir}/references/evidence-templates.md) — Documentation templates for data flow, mathematical proofs, attacker control, and devil's advocate reviews
章节与文件索引
按说明文件中的顺序排列。
何时使用
何时不使用
拒绝的理由
第 0 步:理解主张和背景
路线:标准验证与深度验证
文件/命令 -> parse_header() · content_length · memcpy · bug-class-verification.md · references/bug-class-verification.md · standard-verification.md · references/standard-verification.md · deep-verification.md
内容校验值 -> eb34a0acf784
当前原文的自动摘译,尚未人工审校。
何时使用
“这个错误是真的吗?”或“这是真正的阳性结果吗?” “这是误报吗?”或“验证此发现”“检查此漏洞是否可利用”任何验证或验证特定可疑错误的请求
何时不使用
查找或寻找错误(“查找错误”、“安全分析”、“审核代码”) 针对样式、性能或可维护性的一般代码审查 功能开发、重构或非安全任务 当用户明确要求快速扫描而不进行验证时
拒绝的理由
如果你发现自己有这些想法,请停止。合理化 · 错误的原因 · 需要采取的行动 “快速分析剩余的 bug” · 每个 bug 都得到全面验证 · 返回任务列表,通过所有阶段验证下一个 bug “这个模式看起来很危险,所以它是一个漏洞” · 模式识别不是分析 · 在得出任何结论之前完成数据流跟踪 “为了提高效率,跳过全面验证” · 不允许部分分析 · 按照所选验证路径执行所有步骤
路线:标准验证与深度验证
步骤0之后,选择验证路径。