High severityGoSSRF & Path TraversalMEDIUM confidence
SSRF HTTP Request
A user-controlled value is used as the URL of an outbound HTTP request, enabling server-side request forgery (CWE-918).
Standards mapping
- OWASP Top 10
- A10:2021 - Server-Side Request Forgery (SSRF)
- OWASP ASVS
- V12.6.1 (L1)
Vulnerable vs. safe
Flagged by this check
_, _ = http.Get(target)Passes - the safe pattern
_, _ = http.Get("https://api.internal.example.com/health")Why it matters & how to fix it
A user-controlled value is used as the URL of an outbound HTTP request, enabling server-side request forgery (CWE-918). An attacker can pivot to internal services, cloud metadata endpoints, or link-local addresses. Validate the target against an allow-list of schemes/hosts, resolve the hostname and reject private/loopback/link-local IPs, and disable automatic redirects for sensitive fetches.
References
Rule ID integsec-go-ssrf-http-request - engine: Opengrep - license: MIT - Copyright (c) IntegSec Inc.
TurboPentest runs this check automatically
Connect a GitHub repo and this check runs on every white-box pentest - AI-validated and reported with proof, from $99 per target.
Start a pentestRelated checks
- JavaScript / TypeScript - SSRF & Path TraversalPath Join With Request
- JavaScript / TypeScript - SSRF & Path TraversalPath Traversal Tainted Input
- JavaScript / TypeScript - SSRF & Path TraversalSSRF Outbound Request Tainted Input
- Python - SSRF & Path TraversalPath Traversal
- Python - SSRF & Path TraversalSSRF HTTP Request
- Java - SSRF & Path TraversalPath Traversal Tainted Input