const isLocalhost = (url) => host === '::1'; ; if (isLocalhost(url)) return res.status(400).send('Localhost requests blocked');
http://[::1]:3000/encryptionkey.txt
Abstract Server-Side Request Forgery (SSRF) remains a critical web security vulnerability, often enabling internal network reconnaissance, port scanning, and cloud metadata theft. OWASP Juice Shop, a modern intentionally vulnerable web app, contains multiple SSRF challenges that simulate real-world misconfigurations. This paper dissects the Juice Shop SSRF attack surface, demonstrates exploitation techniques, and discusses detection and prevention strategies. 1. Introduction OWASP Juice Shop is a Node.js/Express-based application packed with vulnerabilities from the OWASP Top 10. Among its medium-difficulty challenges is SSRF (Server-Side Request Forgery) — specifically the challenge titled “SSRF” (ID: ssrf ) and related endpoints that allow an attacker to make the server perform arbitrary HTTP requests. owasp juice shop ssrf
curl "http://localhost:3000/api/Image?url=http://localhost:3000/encryptionkey.txt" HTTP 200 with the encryption key in the body (may be text/plain despite image content-type header). 5. Impact Assessment | Attack Vector | Impact | |---------------|--------| | Localhost file read | Exposure of source code, config files, secrets | | Internal port scan | Discovery of admin panels, databases, Redis, Jenkins | | Cloud metadata theft | IAM credentials, access tokens → cloud account compromise | | Service interaction (e.g., Redis, Memcached) | Potential RCE via protocol smuggling | const isLocalhost = (url) => host === '::1';