Install
$ agentstack add skill-netw0rknoob-vulnclaw-redteam-cve-validation ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
CVE Validation
Domain
Validate candidate CVEs against the current target evidence without assuming exploitability. The module consumes cve_candidate_list, product/version evidence, service fingerprints, and scope data, then decides whether the CVE path is usable, patched, not applicable, or needs more recon.
Trigger
cve_candidate_list_ready
Feedback Gates
- Scope Gate: target and asset must be in the declared authorization boundary.
- Evidence Gate: candidate CVE must map to observed product, version, endpoint, service, or fingerprint evidence.
- Applicability Gate: version range, configuration, and reachable component must plausibly match.
- Patch Gate: observed version or vendor advisory must not prove the issue fixed.
- Execution Gate: active validation requires a registered scoped adapter; missing adapters block rather than pretending execution happened.
Boundaries
- Do not run destructive or broad exploit attempts.
- Do not validate outside the declared target and scope.
- Do not treat CVE names alone as proof.
- Prefer passive or low-noise confirmation first.
- If evidence is insufficient, return to recon or CVE lookup rather than guessing.
Pivot Hints
- Candidate has no product/version match -> return to recon-intake for better fingerprinting.
- Candidate is patched or not applicable -> route by highest-ranked attack surface from recon.
- Tool or adapter missing -> record missing capability and request/choose an equivalent adapter.
- Too many candidates -> rank by reachable component, confidence, impact, and version fit.
Exit Conditions
- Confirmed applicable candidate -> continue to the specific validation/testing skill.
- All candidates patched/not applicable -> exit to evidence-based router.
- Evidence incomplete -> return to recon-intake or cve-lookup.
- Required tool/scope/adapter missing -> block with the missing capability or scope evidence.
Exit Evidence
- Required: cvevalidationresult
- Optional: cvepatchstatus, applicabilityproof, nonapplicability_reason
- min_attempts: 1
Capabilities
cve_applicability -> cve_validation_result
patch_status_check -> cve_patch_status
page_fetch -> applicability_proof
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Netw0rkNoob
- Source: Netw0rkNoob/VulnClaw
- License: MIT
- Homepage: https://unclecheng-li.github.io/vulnclaw.com
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.