Src Component Nday

TL;DR

• 目的：Component N-day hunting workflow (main pipeline)
• 适用：通用型漏洞报告主流程
• 输入：目标 URL + 工作模式（A 项目 / B SRC / LAB）
• 输出：完整 PoC + 报告草稿
• 红线：A 模式全 RCE 需二次确认；B 模式爆破 ≤10
• 关联：上游：src-session-start → 下游：component-nday, cve-poc-generator, fp-check, reporting

When to Use

• Target presents indicators of the vulnerability class this skill covers
• Fingerprint or recon indicates the relevant technology stack is in use
• Authorized testing scope covers the target endpoint or component
• Findings need to be validated through this skill's methodology

When NOT to Use

• Target is clearly outside this skill's scope (refer to related skills)
• No authorization for testing
• Need a different category of testing (use related skills)

Workflow

1. Recon — Run 010-hunt-subdomain to find target
2. Fingerprint — Use Wappalyzer / nuclei to detect components
3. CVE match — Use kev + component-nday to find known CVEs
4. PoC — Use cve-poc-generator for known CVEs
5. Verify — Use fp-check for cross-validation
6. Report — Use project-pentest / cnvd-common / edusrc template

Advanced Techniques

Main Pipeline Coordination

This skill orchestrates: component-nday (fingerprint) + kev (prioritize) + cve-poc-generator (exploit) + fp-check (validate) → report.

Subdomain Coverage

For multi-subdomain targets, run component-nday on each subdomain to find different component versions. Different subdomains often use different stacks.

Historical Version Detection

Wayback Machine, Shodan historical data, and Censys certificates can reveal previous component versions that may still be accessible at unpatched endpoints.