Agent Skills
› Unclecheng-li/VulnClaw
› cve-triage
cve-triage
GitHub用于将侦察获取的服务版本信息映射至已知CVE，基于CVSS和可利用性进行评分与优先级排序，指导安全验证工作流。
Trigger Scenarios
发现服务版本或Banner信息
需要评估特定软件版本的漏洞风险
Install
npx skills add Unclecheng-li/VulnClaw --skill cve-triage -g -y
SKILL.md
Frontmatter
{
"name": "cve-triage",
"routing": {
"phases": [
"vuln_discovery"
],
"task_types": [
"triage"
]
},
"description": "CVE lookup and triage — map discovered services\/versions to known CVEs via the cve_lookup tool, score by CVSS\/exploitability, and prioritize what to verify first."
}
CVE Triage
Turn version/banner evidence from recon into a prioritized, exploitability-aware
list of CVEs worth verifying. Use this after fingerprinting a service, when a
banner or Server: header reveals a product and version, or whenever the target
exposes software with a known version.
The cve_lookup tool
VulnClaw ships a read-only cve_lookup tool backed by NVD:
- Keyword search —
cve_lookup(query="Apache httpd 2.4.49", limit=5)returns the top CVEs sorted by CVSS, highest first. - CVE-ID detail —
cve_lookup(query="CVE-2021-44228")returns the full record plus best-effort exploit / PoC repositories discovered on GitHub.
It performs no egress to the target and is safe during recon. Without an
NVD_API_KEY it still works (lower rate limit); set one for heavier use.
Workflow
- Extract product + version from recon — service banners,
Serverheaders, JS bundles, login footers, package manifests. A precise version string (OpenSSH 8.2p1,nginx 1.18.0) yields far better matches than a bare name. - Query
cve_lookupwith"<product> <version>". Pull the detail record for any high/critical hit by re-querying itsCVE-ID. - Score & prioritize — see
references/cve-triage-workflow.md. Rank by CVSS, then by exploit availability, then by exposure (is the vulnerable surface actually reachable on this target?). - Confirm version applicability — match the target's version against the
CVE's affected
cperange before claiming it. Banner ≠ proof of vulnerability. - Record findings with the CVE-ID, CVSS, and the evidence that maps this target to it. Mark unconfirmed version-only matches as needs-manual-review, not verified.
Pitfalls
- A keyword match is a hypothesis, not a finding — version ranges and backported patches mean a banner version can be patched in place.
- GitHub "PoC" repos are unverified third-party code; treat as leads, never run blindly against a target.
- Prefer the CVSS base score for triage, but let exploit availability and real exposure override raw score when prioritizing verification effort.
Version History
- fcad047 Current 2026-07-11 17:52
