ajtazer/heckit / skills/cve-hunting/cve-hunting-methodology
cve-hunting-methodology
UnverifiedCross-cutting methodology for the CVE-hunting pipeline (ported from find-cve-agent): when a bug is design-vs-real, false-positive avoidance, version checking before reporting, responsible disclosure norms, acceptance-rate expectations per vuln class, vulnerability chaining playbook, known false-positive patterns, maintainer-response patterns, secure-pattern reference (what NOT to flag), and a self-criticism checklist to run before claiming a finding. Use this alongside the cve-hunter/cve-exploiter/cve-validator agents and the /cve-hunt pipeline — load it whenever judging if a finding is real, worth reporting, or already fixed.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.7 KB |
| references/acceptance-rates.md | markdown | 12.1 KB |
| references/chaining-playbook.md | markdown | 10.3 KB |
| references/design-vs-bug.md | markdown | 3.6 KB |
| references/disclosure-channels.md | markdown | 11.0 KB |
| references/false-positive-avoidance.md | markdown | 4.0 KB |
| references/false-positive-patterns.md | markdown | 12.0 KB |
| references/maintainer-responses.md | markdown | 11.6 KB |
| references/rejection-taxonomy.md | markdown | 12.0 KB |
| references/responsible-disclosure.md | markdown | 2.4 KB |
| references/secure-patterns.md | markdown | 15.0 KB |
| references/self-criticism-checklist.md | markdown | 10.2 KB |
| references/version-checking.md | markdown | 2.4 KB |
references/version-checking.md
View on GitHub# Version Checking — Always Verify the Exact Version
**Reporting vulnerabilities in already-patched versions is the #1 embarrassment in security research.**
## Why This Matters
- Maintainers lose trust in researchers who report fixed bugs
- It wastes everyone's time and clutters advisory databases
- Your credibility drops with every false report
## Verification Process
### Step 1: Identify the Exact Installed Version
```bash
# npm
cat node_modules/<package>/package.json | grep '"version"'
npm ls <package>
# PyPI
pip show <package> | grep Version
# Go
grep <package> go.sum
go list -m <package>
# Ruby
bundle show <gem> | grep -i version
```
### Step 2: Check for Existing CVEs on That Version
```bash
# NVD
./scripts/check-nvd.sh <package-name>
# OSV.dev (version-specific)
./scripts/check-osv.sh npm <package-name> <version>
./scripts/check-osv.sh PyPI <package-name> <version>
# GitHub Advisory Database
gh api graphql -f query='{ securityVulnerabilities(ecosystem:NPM, package:"<package>", first:10) { nodes { advisory { summary ghsaId } vulnerableVersionRange firstPatchedVersion { identifier } } } }'
```
### Step 3: Check the CHANGELOG
Look for entries containing: "security", "fix", "CVE", "vulnerability", "patch", "sanitize", "escape", "validate"
```bash
# In the cloned repo
grep -i "security\|CVE\|vulnerab\|sanitiz\|escap" CHANGELOG.md CHANGES.md HISTORY.md 2>/dev/null
git log --oneline --grep="security\|CVE\|fix" --since="1 year ago"
```
### Step 4: Check Git History for Security Commits
```bash
git log --all --oneline --grep="security" --grep="CVE" --grep="vulnerability" --grep="injection" --grep="traversal" --grep="XSS"
```
### Step 5: Test Against Latest Release
```bash
# Always install latest before testing
npm install <package>@latest
pip install --upgrade <package>
```
**Never test only against the version in your local node_modules — it may be outdated.**
## Common Pitfalls
| Pitfall | Example | How to Avoid |
|---------|---------|--------------|
| Testing old version | Testing qs@6.5.2 when 6.14.2 is latest | Always `npm install <pkg>@latest` |
| Missing patch release | Bug fixed in 2.3.1, testing 2.3.0 | Check all patch versions |
| Different package name | Confusing `xml2js` with `xml-js` | Verify exact package name in NVD |
| Backported fix | Fix backported to LTS branch | Check all maintained branches |
| Pre-release fix | Fixed in 3.0.0-beta but not 2.x | Note which versions are affected |
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 |