Individual skill

performing-blind-ssrf-exploitation

Detect and exploit blind Server-Side Request Forgery vulnerabilities using out-of-band techniques, DNS interactions, and timing analysis to access internal services and cloud metadata endpoints.

internal/tools/skills/data/web-application-security/performing-blind-ssrf-exploitation/SKILL.md

Read pinned source

Source commit d42f381ad34843e71a42658e5c57290c713e85af

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,313
Repository last updated
Nov 8, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Performing Blind SSRF Exploitation

## When to Use
- When testing URL/webhook input parameters where server-side responses are not reflected
- During assessment of applications that fetch external resources (avatars, previews, imports)
- When testing PDF generators, image processors, or document converters for SSRF
- During cloud security assessments to detect metadata endpoint access
- When evaluating webhook functionality and URL validation implementations

## How to CONFIRM a Hit (avoid false negatives)

Blind SSRF returns no reflected response, so confirmation rests **entirely on out-of-band (OOB) signals** — never infer success or failure from the HTTP status code alone:
- **Unique-subdomain DNS hit:** embed a per-test subdomain (`<test-id>.<your-id>.oast.fun`) so each payload is attributable; an inbound **DNS lookup** confirms the server resolved your host even when outbound HTTP is firewalled.
- **HTTP/FTP callback:** an inbound request landing on your `interactsh`/Collaborator/webhook.site listener proves full server-side egress.