ajtazer/heckit / skills/cve-hunting/fp-check
fp-check
VerifiedSystematic false positive elimination for security findings. 6-gate verification, 13-item checklist, devil's advocate questioning. MANDATORY before any CVE submission.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.4 KB |
| references/bug-class-verification.md | markdown | 2.0 KB |
| references/deep-verification.md | markdown | 3.1 KB |
| references/evidence-templates.md | markdown | 2.0 KB |
| references/false-positive-patterns.md | markdown | 2.7 KB |
| references/gate-reviews.md | markdown | 1.8 KB |
| references/standard-verification.md | markdown | 2.8 KB |
references/gate-reviews.md
View on GitHub# Gate Reviews and Verdicts
Before reporting ANY bug as a vulnerability, all six gate reviews must pass.
| Gate | Criterion | Pass | Fail |
|------|-----------|------|------|
| **1. Process** | All phases completed with documented evidence | Evidence exists for every phase | Phases lack concrete evidence |
| **2. Reachability** | Attacker can reach and control data at the vulnerability | Clear evidence of attacker-controlled path + PoC confirms | Cannot demonstrate attacker control or reachability |
| **3. Real Impact** | Exploitation leads to RCE, privesc, or info disclosure | Direct impact with concrete scenarios | Only operational robustness issue |
| **4. PoC Validation** | PoC demonstrates the attack path | Shows attacker control, trigger, and impact | PoC fails to show attack path or impact |
| **5. Math Bounds** | Mathematical analysis confirms vulnerable condition is possible | Algebraic proof shows condition is possible | Math proves validation prevents it |
| **6. Environment** | No environmental protections entirely prevent exploitation | Protections do not eliminate vulnerability | Environmental protections block it entirely |
## Verdict Format
- **TRUE POSITIVE**: All gate reviews pass
`BUG #N TRUE POSITIVE -- [brief vulnerability description]`
- **FALSE POSITIVE**: Any gate review fails
`BUG #N FALSE POSITIVE -- [brief reason for rejection]`
If any phase fails verification, document the failure with evidence and continue all remaining phases. Issue the FALSE POSITIVE verdict only after all phases are complete.
## Example Verdict
```
BUG #3 FALSE POSITIVE -- Integer underflow in packet_handler.c:142
Gate 5 (Math Bounds) FAIL: validation at line 98 ensures packet_size >= 16,
making (packet_size - header_size) >= 8. Underflow is mathematically impossible.
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |