hunt-ssrf

Map URL parameters and confirm SSRF sinks via out-of-band callbacks.

2|Updated Apr 11, 2025
One-click install
npx skills add https://github.com/Carlos-Reyes-UTP/Desarrollo-de-Sistema-de-Ventas-Empresas-de-Moda --skill hunt-ssrf-carlos-reyes-utp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-ssrf
Source: https://github.com/Carlos-Reyes-UTP/Desarrollo-de-Sistema-de-Ventas-Empresas-de-Moda/tree/main/.agent/skills/hunt-ssrf
Command: npx skills add https://github.com/Carlos-Reyes-UTP/Desarrollo-de-Sistema-de-Ventas-Empresas-de-Moda --skill hunt-ssrf-carlos-reyes-utp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you systematically identify and validate SSRF vulnerabilities by focusing on high-likelihood URL fetch surfaces and enforcing out-of-band confirmation to avoid false positives.

Core Features & Use Cases

  • Crown-jewel targeting: Prioritizes SSRF sinks in cloud metadata environments, internal platforms (Kubernetes), link preview/unfurling, and import/fetch pipelines.
  • OOB-or-it-didn’t-happen gating: Requires DNS/HTTP callbacks (e.g., Collaborator/interactsh/canarytokens) before claiming impact, preventing “echo-only” misclassification.
  • Practical methodology: Guides URL-parameter mapping, blind SSRF checks, internal/local metadata probing, redirect-chain testing, and JS/headless SSRF scenarios.
  • Impact-oriented validation: Emphasizes credential theft and internal admin/data exfil chains to support defensible reporting.

Quick Start

Use the hunt-ssrf skill to validate suspected URL-fetching endpoints by planting a unique out-of-band callback domain first, then confirming the target makes a real outbound request before documenting the SSRF scope and impact.

Frequently Asked Questions about hunt-ssrf

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

FAQPage Schema
How do I validate blind SSRF vulnerabilities with out-of-band callbacks?

Validate blind SSRF vulnerabilities by planting a unique out-of-band callback domain and confirming the target makes a real outbound DNS or HTTP request before documenting impact. This strict gating prevents false positives from echo-only responses.

What is the best way to test for SSRF in cloud metadata environments?

Testing for SSRF in cloud metadata environments requires prioritizing high-likelihood URL fetch surfaces and probing internal endpoints. Focus on link preview, proxy, and import features to target credential theft and internal admin data exfiltration chains.

How do I bypass redirect restrictions when testing SSRF sinks?

Bypass redirect restrictions by applying redirect-chain testing to URL parameters and JS/headless rendering contexts. This methodology validates redirect-following fetchers to ensure internal network probing reaches protected services.

Does SSRF vulnerability hunting work for Kubernetes internal platforms?

SSRF vulnerability hunting works for Kubernetes internal platforms by mapping URL/URI parameters and detecting likely sinks. Priority checks against internal services ensure comprehensive coverage for cloud-hosted deployments.

Why does my SSRF scanner report false positives on link preview features?

SSRF scanners report false positives on link preview features when they lack out-of-band confirmation. Requiring DNS or HTTP callbacks before claiming impact ensures only verified outbound requests are documented as vulnerabilities.