ssrf-server-side-request-forgery

SSRF testing involves injecting internal URLs or cloud metadata endpoints into URL fetch parameters to detect unauthorized resource access. This Skill automates detecting Server-Side Request Forgery by testing target applications for accessible internal services and exposed cloud metadata endpoints during authorized penetration tests.

Bypassing SSRF URL filters requires techniques like protocol abuse using gopher, dict, or file schemes to access restricted internal resources. This Skill provides an exploitation playbook covering various filter bypass methods and protocol abuse techniques to reach internal services that standard assessments often miss.

Yes, SSRF attacks can access AWS, GCP, Azure, and Alibaba Cloud metadata endpoints to steal cloud credentials and sensitive resources. This Skill includes pre-built payloads specifically targeting cloud metadata services and Kubernetes APIs to extract unauthorized cloud configuration data.

Blind SSRF detection identifies vulnerabilities by monitoring out-of-band interactions or timing delays when the target application processes injected internal URLs. This Skill covers blind detection techniques alongside methods to chain SSRF into remote code execution via internal services like Redis and Docker.

Chaining SSRF to RCE exploits internal services by abusing protocols like gopher to send crafted commands to Redis or Docker APIs. This Skill provides step-by-step exploitation guides for compromising internal services and chaining public vulnerabilities like WebLogic SSRF to achieve remote code execution.

Yes, it provides step-by-step exploitation guides for public Server-Side Request Forgery vulnerabilities including WebLogic SSRF (CVE-2014-4210) and Kubernetes SSRF (CVE-2020-8555/8562). These real-world CVE chains demonstrate how to compromise internal services during authorized security testing.