INJ-006critical SeverityInjection Sinks & Input Validation
Server-Side Request Forgery (SSRF) Protection on URL Fetchers
When building preview scrapers or webhook testers, AI uses fetch(req.body.url) without blocking loopback IPs or cloud metadata endpoints.
1-Click Fix Prompt for Cursor & Claude Code
Review my codebase for "Server-Side Request Forgery (SSRF) Protection on URL Fetchers" (INJ-006). Issue: When building preview scrapers or webhook testers, AI uses fetch(req.body.url) without blocking loopback IPs or cloud metadata endpoints. Remediation required: Reject internal IP addresses (127.0.0.1, 10.0.0.0/8, 169.254.169.254) and allow only public HTTPS hostnames. Please: 1. Locate any occurrences of this issue across my repository. 2. Refactor the code to follow production standards without breaking existing functionality. 3. Provide a clear command or step to test and verify the fix.
Why AI Assistants Write This Bug
When building preview scrapers or webhook testers, AI uses fetch(req.body.url) without blocking loopback IPs or cloud metadata endpoints.
AI code generation prioritizes immediate syntax execution over production edge cases. When an assistant hits an undefined variable or strict type error, it frequently takes the path of least resistance rather than implementing standard pre-launch security patterns.
Code Comparison
Common AI Code PatternVulnerable
// Vulnerable AI-generated pattern for: Server-Side Request Forgery (SSRF) Protection on URL Fetchers
// Problematic pattern: When building preview scrapers or webhook testers, AI uses fetch(req.body.url) without blocking loopback IPs or cloud metadata endpoints.Launch-Ready Fix
// Production-ready fix for: Server-Side Request Forgery (SSRF) Protection on URL Fetchers
// Recommended remediation: Reject internal IP addresses (127.0.0.1, 10.0.0.0/8, 169.254.169.254) and allow only public HTTPS hostnames.Remediation & Verification Checklist
Remediation: Reject internal IP addresses (127.0.0.1, 10.0.0.0/8, 169.254.169.254) and allow only public HTTPS hostnames.
- Search your codebase for pattern matching "Server-Side Request Forgery (SSRF) Protection on URL Fetchers".
- Apply the recommended remediation: Reject internal IP addresses (127.0.0.1, 10.0.0.0/8, 169.254.169.254) and allow only public HTTPS hostnames.
- Run local build and test commands to ensure no regressions.
- Verify in your browser or with curl that the issue is resolved.
Audit All 108 Checks in One Click
Checking items one by one takes hours. Let us do it in 2 minutes.
With the Founder Pass ($15 one-time), we automatically scan your repository for this issue, plus all other 107 launch checks across secrets, Stripe webhooks, Supabase RLS, and security headers.