dependency-cve

Fingerprint application frameworks and library versions to identify vulnerable dependencies.

54|5|Updated May 9, 2026
One-click install
npx skills add https://github.com/jinyimeng01/mastermind-bug-bounty --skill dependency-cve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-cve
Source: https://github.com/jinyimeng01/mastermind-bug-bounty/tree/main/skills/dependency_cve
Command: npx skills add https://github.com/jinyimeng01/mastermind-bug-bounty --skill dependency-cve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps security teams identify vulnerable software dependencies by fingerprinting frameworks, libraries, and versions across web applications and mapping them to known CVEs.

Core Features & Use Cases

  • Dependency Fingerprinting: Detects technologies through JavaScript files, headers, cookies, error pages, default paths, and exposed metadata.
  • CVE Matching Guidance: Connects identified versions with common vulnerability classes across frameworks such as Spring, Fastjson, Shiro, Log4j, Laravel, and WordPress.
  • Security Validation Workflow: Provides safe verification approaches for confirmed risks, including non-destructive checks and reporting guidance.

Quick Start

Use the dependency-cve skill to analyze a target application's exposed technologies and identify potential vulnerable dependencies.

Frequently Asked Questions about dependency-cve

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify vulnerable software dependencies through web application fingerprinting?

You can fingerprint web application frameworks and library versions by analyzing exposed JavaScript files, HTTP headers, cookies, error pages, and default paths, then mapping the detected technologies to known CVEs for vulnerability triage.

What is the process for matching detected framework versions to known CVEs during security assessments?

Matching detected framework versions to known CVEs involves correlating the identified library versions with common vulnerability classes across frameworks like Spring, Fastjson, Shiro, Log4j, Laravel, and WordPress to pinpoint potential security risks.

How do I safely validate security findings for exposed technology stacks without causing damage?

Safely validating security findings for exposed technology stacks requires applying non-destructive checks and following safe verification approaches to confirm vulnerable dependencies before reporting the identified risks.

Can I use dependency fingerprinting for bug bounty reconnaissance on exposed technology stacks?

Yes, dependency fingerprinting is applicable for bug bounty reconnaissance, as it detects exposed technologies and maps identified framework versions to known vulnerabilities within the target application's technology stack.

What technologies can be detected when fingerprinting application frameworks for vulnerability triage?

Technologies detected during fingerprinting for vulnerability triage include frameworks and libraries such as Spring, Fastjson, Shiro, Log4j, Laravel, and WordPress, identified through metadata, headers, and default paths.