Turn observed software names and versions into a prioritized list of known vulnerabilities using cve_lookup. Rank candidates by severity, available exploit code, and actual exposure, while keeping unconfirmed version matches clearly separate from verified findings.
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.
Review the instructions the agent will receive before you install.
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.
cve_lookup toolVulnClaw ships a read-only cve_lookup tool backed by NVD:
cve_lookup(query="Apache httpd 2.4.49", limit=5) returns
the top CVEs sorted by CVSS, highest first.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.
Server headers,
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.cve_lookup with "<product> <version>". Pull the detail record for
any high/critical hit by re-querying its CVE-ID.references/cve-triage-workflow.md. Rank by CVSS,
then by exploit availability, then by exposure (is the vulnerable surface
actually reachable on this target?).cpe range before claiming it. Banner ≠ proof of vulnerability.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Assess AI agents and MCP tools for malicious instructions, tool misuse, permission violations, and data leaks. The skill organizes checks across applications, identity, data, deployment, and models, with references for each risk area.
Test Android app security by operating the app and inspecting network traffic first, then analyzing APK code or observing functions during execution when needed. Verify vulnerabilities and produce a report with screenshots, traffic evidence, and code review findings.
Analyze traffic from Android apps, browser JavaScript, and desktop clients to prepare requests for replay in Burp. Investigate signatures, encryption, and session dependencies when they block replay, and retain working request samples with supporting observations.
Handle encoded strings and cryptographic data with tool-based conversions. Decode layered formats, calculate hashes, encrypt or decrypt with AES and RSA, and inspect JWT tokens, which carry encoded headers and data used in authentication.
Analyze CTF cryptography challenges by identifying the cipher and matching known parameters to possible attacks. It provides formulas, attack parameters, and Python snippets for RSA, AES, elliptic curves, random number generators, classical ciphers, and lattice problems.
Find relevant references for CTF miscellaneous challenges, including restricted execution environments, layered encodings, hidden data in media, and game or virtual machine analysis. It also covers CTFd platform operations and Linux privilege escalation.