Skip to content

ajtazer/heckit / skills/cve-hunting/fp-check

fp-check

Verified

Systematic false positive elimination for security findings. 6-gate verification, 13-item checklist, devil's advocate questioning. MANDATORY before any CVE submission.

references/evidence-templates.md

View on GitHub
# Evidence Templates

## Data Flow Documentation

```
Bug #N Data Flow Analysis
Source: [exact location] -- Trust Level: [trusted/untrusted]
Path: Source -> Validation1[file:line] -> Transform[file:line] -> Vulnerability[file:line]
Validation Points:
  - Check1: [condition] at [file:line] -- [passes/fails/bypassed]
  - Check2: [condition] at [file:line] -- [passes/fails/bypassed]
```

## Mathematical Bounds Proof

```
Bug #N Mathematical Analysis
Claim: Operation X is vulnerable to [overflow/underflow/bounds violation]
Given Constraints: [list all validation conditions]

Algebraic Proof:
1. [first constraint from validation]
2. [constant or known value]
3. [derived inequality]
...
N. Therefore: [vulnerability confirmed/debunked] (Q.E.D.)
```

Example:
```
Given: validation ensures (input_size >= MIN_SIZE)
Given: MIN_SIZE = 16, header_size = 8
1. input_size >= 16                   (from validation)
2. input_size - 8 >= 8               (subtract header_size)
3. Therefore: underflow impossible    (Q.E.D.)
```

## Attacker Control Analysis

```
Bug #N Attacker Control Analysis
Input Vector: [how attacker provides input]
Control Level: [full/partial/none]
Constraints: [limits on attacker input]
Reachability: [can attacker-controlled data reach vulnerable operation?]
```

## PoC -- Pseudocode with Data Flow Diagram

```
PoC for Bug #N: [Brief Description]

[External Input] -> [Validation Point] -> [Processing] -> [Vulnerable Operation]
     |                    |                   |                    |
  Attacker           (May be bypassed)    (Transforms)        (Unsafe op)

PSEUDOCODE:
function vulnerable_operation(user_data):
    validation_result = weak_validation(user_data)
    processed_data = transform_data(user_data)
    unsafe_operation(processed_data)
```

## Devil is Advocate Review

```
Bug #N Devil is Advocate Review
Vulnerability Claim: [brief description]

1-5. [Challenges arguing AGAINST the vulnerability]
6-7. [Challenges arguing FOR the vulnerability]

Final Assessment: [confirmed/debunked with reasoning]
```
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall