Server-Side Request Forgery (SSRF)
A route through the library rather than a dump of it. Items are drawn from the full SSRF collection, filtered to teaching material (news items are excluded) and ordered within each stage by depth signals — whether the piece carries code, how substantial it is, and what readers actually open.
1
Start here
5 resourcesOrientation and first principles — what the bug class is and how it behaves.
- Preventing server-side request forgery in Node.js applicationsTool for preventing server-side request forgery (SSRF) in Node.js applications, detailing how attackers exploit input tampering and URL manipulation to make unintended server requests. It covers basic and blind SSRF types, referencing a significant Amazon breach. Mitigation strategies include using updated libraries, employing firewalls, sanitizing user input, enforcing URL schemas like HTTP/HTTPS, and creating allowlists for trusted domains, exemplified by code adjustments in an Express and Axios application.
- PayloadsAllTheThings: Server Side Request ForgeryLibrary for Server Side Request Forgery (SSRF) vulnerabilities, detailing methodologies and bypass techniques. It covers bypassing localhost via IPv6 notation, domain redirects, CIDR, rare addresses, encoded IPs, and DNS rebinding. The library highlights exploitation via URL schemes like `jar:` and `gopher://`, blind exploitation, and offers tools such as `SSRFmap`, `Gopherus`, `See-SURF`, `SSRF-Sheriff`, `surf`, `ipfuscator`, and `r3dir` for testing and exploitation.
- SSRF Explained: Attack Techniques and Real-World ExploitsLibrary detailing Server-Side Request Forgery (SSRF) attack techniques, including exploiting cloud metadata endpoints on AWS, GCP, and Azure, bypassing blocklists with alternative IP representations and DNS rebinding, abusing URL schemes like `file://`, `dict://`, and `gopher://`, chaining open redirects, and accessing internal services like Kubernetes APIs and admin panels. It also covers blind SSRF, out-of-band detection, and exploitation via server-side PDF generation using `wkhtmltopdf`.
- Server-Side Request Forgery (SSRF) | InvictiLibrary detailing Server-Side Request Forgery (SSRF), a vulnerability (CWE-918) allowing attackers to trick a server into sending unintended requests. This can expose sensitive data, internal networks, and cloud credentials, as seen in the Capital One breach. The library covers SSRF exploitation techniques, including accessing localhost, internal IPs, and cloud metadata services via HTTP/S, file schemas, and insecure XML parsing, contrasting it with CSRF and outlining prevention strategies like URL validation and protocol restriction.
- Server-Side Request Forgery: What It Is & How To Fix It | WizLibrary detailing Server-Side Request Forgery (SSRF) vulnerabilities, explaining how attackers trick servers into making requests to internal resources like cloud metadata services and sensitive systems. It highlights SSRF's inclusion in the OWASP Top 10 and CWE Top 25, with examples like the Capital One breach. The library emphasizes prevention through strict input validation, egress controls, API security best practices, and continuous API inventory management, referencing tools like SSRFire and ZAP for detection.
2
Build depth
5 resourcesReal testing methodology, tooling, and writeups that show the work.
- The HTTP 303 SSRF Hack : From Python HTTP Client Defaults to AWS Credential Exfiltration.Writeup detailing an HTTP 303 SSRF vulnerability that escalates to AWS credential exfiltration. This exploit chains a user-controlled `token_uri` field in BigQuery service account credentials, an HTTP client with default redirect handling, and the AWS Instance Metadata Service (IMDS). By configuring a server to respond with an HTTP 303 redirect, a POST request to IMDS is implicitly converted to a GET request, allowing the attacker to retrieve temporary IAM credentials for the Kubernetes worker node.
- Catflix CTF: Exploiting SSRFs in Next.js MiddlewareWalkthrough of CVE-2025-57822 in Next.js Middleware, chaining SSRF to RCE via Jenkins. This article details exploiting a misconfiguration in Next.js middleware that allows processing of the `Location` header to perform server-side requests. The SSRF is then escalated by identifying an open Jenkins instance on port 8080, enabling command execution through its Groovy Script console to retrieve sensitive files, demonstrating a practical vulnerability exploitation chain.
- DNS Rebinding Attacks Against SSRF ProtectionsLibrary for detecting and exploiting DNS rebinding vulnerabilities that bypass SSRF protections. It details how applications resolve hostnames once to validate IPs against blocklists or allowlists, and then resolve again to make the actual HTTP request. This Time-of-Check to Time-of-Use (TOCTOU) flaw allows attackers to control DNS responses, redirecting requests from public IPs to sensitive internal endpoints like AWS IMDS (169.254.169.254) or internal APIs. The library covers techniques and tools like rbndr.us and whonow for setting up controllable DNS servers with zero TTL, and discusses fixes such as resolving once and connecting directly to the IP, using egress proxies like Smokescreen, or implementing network-level controls.
- Exploiting PDF Generators: Complete Guide to SSRFGuide to finding SSRF vulnerabilities in PDF generators, focusing on HTML-to-PDF conversion. It details how unsanitized user input can lead to HTML injection, enabling SSRF, Local File Disclosure (LFD), and other exploits. The guide provides payloads for both full and blind SSRF, including techniques using XHR, Fetch, meta tags, images, and SVG, and explores escalating SSRF in cloud environments targeting metadata endpoints. CVE-2023-33733 is cited as an example of injection leading to code execution.
- Metabadger: Prevent SSRF via Automated IMDSv2 UpgradesTool for preventing SSRF attacks on AWS EC2 by automating upgrades to Instance Metadata Service v2 (IMDSv2). Metabadger diagnoses current IMDS usage, prepares instances for v2, enables mandatory session tokens and header checks, and can disable the service where unnecessary to reduce attack surface. It assists in identifying instances using IAM roles and provides commands to discover metadata service usage and harden configurations across regions, with options to exclude specific instances or perform dry runs.
3
Go deep
8 resourcesNovel research, edge cases, and the techniques that push the class forward.
- The Limitations of Secure SSRF Patches: Advanced BypassesLibrary that analyzes Server-Side Request Forgery (SSRF) bypass techniques, demonstrating how common patches like prefix allowlisting and basic hostname validation fail against crafted payloads. It highlights vulnerabilities exemplified by the ChatGPT-Next-Web case, where naive checks for `https://trusted.com` were bypassed using `@` notation or subdomain tricks like `api.mycompany.com.evil.org`. The library emphasizes the need for defense-in-depth beyond superficial checks to prevent attackers from accessing internal networks or cloud instance metadata.
- The Red Agent POV: How it Reasoned its Way to SSRFLibrary that details a multi-step SSRF exploit against a GCP Cloud Run service. The exploit chains a GitHub URL validation bypass with a double-slash absolute path technique to read sensitive files like `/proc/self/environ` and application source code. The underlying methodology involves iterative attack strategy execution and reflection, focusing on path traversal and URL confusion techniques before the breakthrough bypass.
- Hacking Next.js Targets: Advanced SSRF Exploitation GuideGuide detailing advanced Server-Side Request Forgery (SSRF) vulnerabilities in Next.js applications. It covers exploitation techniques targeting the Image component, Next.js Middleware (CVE-2025-57822), and Server Actions (CVE-2024-34351). The guide highlights how misconfigurations in these features can lead to arbitrary outbound requests and potential data leakage or remote code execution.
- Exploiting SSRF in Cloud-Only Environments: A Deep DiveWalkthrough demonstrating SSRF exploitation in cloud environments like AWS and Azure. This deep dive details how attackers can leverage Server-Side Request Forgery to access sensitive metadata services, internal applications, and cloud functions by manipulating vulnerable endpoints. The guide utilizes tools such as Burp Suite and SSRFmap to showcase real-world attack scenarios, including retrieving AWS access keys and accessing internal admin panels, ultimately leading to potential data theft, privilege escalation, and system compromise.
- MCPwnfluence: SSRF to RCE in Atlassian MCP Server (Pluto Security)Library for securing Atlassian MCP Server, addressing vulnerabilities CVE-2026-27825 (arbitrary file write leading to RCE) and CVE-2026-27826 (SSRF via header injection). These flaws allow unauthenticated users on the local network to execute commands as root by chaining an SSRF vulnerability with an arbitrary file write, enabling overwriting critical files like `.bashrc` or `.ssh/authorized_keys`. The library includes fixes for path validation and SSRF protection, recommending immediate upgrades for affected versions below 0.17.0.
- MCPwnfluence: Critical SSRF to RCE in mcp-atlassian (Pluto Security)Writeup of CVE-2026-27825 and CVE-2026-27826, detailing an unauthenticated SSRF to RCE attack chain in mcp-atlassian. The vulnerabilities, with CVSS scores of 9.1 and 8.2 respectively, allow network-reachable code execution as root by overwriting files or injecting SSRF payloads via Atlassian URL headers. Affecting versions prior to 0.17.0, the findings highlight risks in widely used MCP server deployments.
- SSRF: Advanced Exploitation GuideGuide to advanced SSRF exploitation, this article details how to identify and exploit Server-Side Request Forgery vulnerabilities, including bypassing host and protocol whitelists, leveraging PDF generators, and understanding second-order SSRFs. It provides examples of bypass payloads and discusses how features like profile image loaders, webhook services, and request header processing can be vulnerable, referencing techniques like DNS rebinding and the PayloadsAllTheThings repository for advanced bypasses.
- A Glossary of Blind SSRF Chains – AssetnoteGlossary of Blind SSRF Chains, detailing techniques for exploiting Server-Side Request Forgery when response data is unavailable. It covers methodologies like using SSRF canaries to confirm internal service reachability, leveraging DNS data with tools such as AltDNS for internal host discovery, and identifying side-channel leaks through response errors, sizes, and timings. Specific examples include chaining with internal SSRFs, app-specific open redirects, blind XXE, and mentions of vulnerabilities affecting Confluence, Artifactory, Jenkins, JAMF, and Apache mod_proxy (CVE-2021-40438).