ssrf-testing

Detect SSRF vulnerabilities by testing user-controlled URL inputs against internal services and cloud metadata endpoints.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/dungsnowaxe/prometheus-red-team-bot --skill ssrf-testing-dungsnowaxe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ssrf-testing
Source: https://github.com/dungsnowaxe/prometheus-red-team-bot/tree/main/promptheus/skills/dast/ssrf-testing
Command: npx skills add https://github.com/dungsnowaxe/prometheus-red-team-bot --skill ssrf-testing-dungsnowaxe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies and validates Server-Side Request Forgery (SSRF) vulnerabilities, preventing attackers from accessing internal resources or cloud metadata.

Core Features & Use Cases

  • Comprehensive SSRF Testing: Covers various SSRF types including basic, blind, cloud metadata, and protocol smuggling.
  • Filter Bypass Techniques: Employs advanced methods to bypass common SSRF filters.
  • Use Case: When auditing a web application, use this Skill to automatically test all user-controlled URL inputs for SSRF, ensuring sensitive internal services and cloud credentials are not exposed.

Quick Start

Use the ssrf-testing skill to scan the target URL 'http://example.com/fetch' for SSRF vulnerabilities.

Frequently Asked Questions about ssrf-testing

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

FAQPage Schema
How do I test for SSRF vulnerabilities in web applications?

To test for SSRF vulnerabilities, target user-controlled URL inputs to simulate requests against internal services and cloud metadata endpoints. This validates unauthorized access or data exfiltration by analyzing server responses for CWE-918, CWE-441, and CWE-611.

What is cloud metadata endpoint testing in SSRF?

Cloud metadata endpoint testing in SSRF involves manipulating URL inputs to query internal cloud metadata services. This detects unauthorized access and potential data exfiltration of sensitive cloud credentials from the application's hosting environment.

How can I bypass common SSRF filters during penetration testing?

To bypass common SSRF filters during penetration testing, employ advanced techniques like protocol smuggling and alternative protocols. These methods help evade input restrictions to successfully identify and validate Server-Side Request Forgery vulnerabilities.

Does this SSRF testing approach cover blind SSRF vulnerabilities?

This SSRF testing approach covers blind SSRF vulnerabilities along with basic and cloud metadata types. It comprehensively tests user-controlled URL inputs using protocol smuggling and filter bypass techniques to validate unauthorized resource access.

What is the best way to validate CWE-918 in network security audits?

The best way to validate CWE-918 in network security audits is by automatically testing all user-controlled URL inputs for SSRF. This ensures sensitive internal services and cloud credentials are not exposed to unauthorized external requests.

When do I need to use protocol smuggling for vulnerability scanning?

You need to use protocol smuggling for vulnerability scanning when standard HTTP requests are blocked by input filters. It helps bypass these restrictions to detect Server-Side Request Forgery by simulating requests using alternative protocols.