How to fix: Potential Server-Side Request Forgery (SSRF) Vectors
User-controlled input may be used in server-side HTTP requests.
Why it matters
SSRF allows attackers to access internal resources, cloud metadata services, or internal networks.
SSRF occurs when an application fetches a remote resource without validating the user-supplied URL.
How to fix it
- 1Validate URLs against an allowlist.
- 2Block requests to private IP ranges.
- 3Disable redirects or validate redirect destinations.
Code examples
SSRF prevention
const ALLOWED = ['api.example.com'];
const url = new URL(userUrl);
if (!ALLOWED.includes(url.hostname)) throw new Error('Invalid URL');References
Detected automatically by VulnRadar. The check id is ssrf-vectors, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
Questions
- How severe is Potential Server-Side Request Forgery (SSRF) Vectors?
- VulnRadar rates this high severity in the content category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id ssrf-vectors, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Potential Server-Side Request Forgery (SSRF) Vectors map to?
- It maps to CWE-918. In the OWASP Top 10 it falls under A10:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.