hunt-ssrf

Confirm SSRF vulnerabilities via out-of-band callbacks across URL-fetching endpoints.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/AKasem1/claude-bug-bounty --skill hunt-ssrf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-ssrf
Source: https://github.com/AKasem1/claude-bug-bounty/tree/main/skills/hunt-ssrf
Command: npx skills add https://github.com/AKasem1/claude-bug-bounty --skill hunt-ssrf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Eliminates false positives in SSRF hunting by enforcing out-of-band proof, then helps you systematically find high-impact SSRF sinks and validate real network reachability.

Core Features & Use Cases

  • Out-of-band (OOB) gating for claims: Requires unique collaborator/canary callbacks before concluding SSRF, preventing “echoed URL” misreports.
  • Target-focused SSRF hunting: Guides tests for common URL-fetch endpoints (preview, fetch, import, proxy, render, screenshot, export, validate) and JavaScript-driven fetch contexts.
  • Cloud and internal pivot prioritization: Emphasizes metadata services (GCP/AWS/Azure), localhost/internal ports, and redirect-based bypasses to quantify blast radius for reporting.

Use case example: If a web app supports “link preview” or “URL import,” use this skill to confirm SSRF via a unique OOB marker and then determine whether it reaches cloud metadata, internal APIs, or headless-rendering network contexts.

Quick Start

Use the hunt-ssrf skill to validate SSRF on your target by planting an OOB callback, sending a URL/payload into the suspected preview or fetch parameter, and only reporting after a confirmed collaborator interaction.

Frequently Asked Questions about hunt-ssrf

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

FAQPage Schema
How do I prove an SSRF vulnerability is real and not a false positive?

Find SSRF sinks by testing common URL-fetching endpoints such as link preview, import, proxy, render, screenshot, export, and validate features. Additionally, test JavaScript-driven fetch contexts and redirect-following behaviors to identify where user-supplied URLs are processed server-side.

What is the best way to demonstrate SSRF impact for cloud metadata services?

Demonstrate SSRF impact by chaining payloads to access cloud metadata services like GCP, AWS, or Azure metadata endpoints. Pivot through localhost or internal ports and use redirect bypasses to quantify the blast radius for triage-quality reporting.

Does out-of-band validation work for headless rendering and JavaScript fetch contexts?

Yes, out-of-band validation works for headless rendering and JavaScript fetch contexts. You plant an OOB callback URL into the suspected fetch parameter, and if the headless browser or JavaScript engine processes it, the collaborator interaction confirms the SSRF.

How do I structure SSRF bug bounty reports to ensure they are accepted during triage?

Structure SSRF reports by including unique OOB collaborator interactions as mandatory proof, documenting the discovered sink endpoint, detailing payload selection, and demonstrating chained impact like internal network reachability for reproducible triage-quality reporting.