How to fix: got / node-fetch / undici with user URL
got(req.query.url), undici.fetch(userUrl), or node-fetch(requestUrl) perform HTTP from the server process. Without URL allowlisting, attackers route requests to internal infrastructure.
Why it matters
SSRF via popular HTTP clients exposes internal services and cloud metadata endpoints.
The `code-ssrf-got-user-input` check verifies that the server does not expose the `ssrf-got-user-input` weakness in the code category. The detection runs against the response headers, body, or auxiliary probes (DNS, TLS, async fetch) as appropriate.
How to fix it
- 1Validate the URL against an allowlist of permitted hosts and ports.
- 2Resolve the hostname and reject loopback / RFC1918 / link-local addresses.
- 3Disable automatic redirects or re-validate after each hop.
Code examples
Restrict got to an allowlisted prefixUrl
import got from "got";
// Use prefixUrl to confine all requests to a known origin
const api = got.extend({
prefixUrl: "https://api.trusted.com/v1",
timeout: { request: 5_000 },
});
// api.get("resource") always goes to api.trusted.com, not arbitrary URLsReferences
Detected automatically by VulnRadar. The check id is code-ssrf-got-user-input, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is got / node-fetch / undici with user URL?
- VulnRadar rates this high severity in the code 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 code-ssrf-got-user-input, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does got / node-fetch / undici with user URL 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.