Packages / fast-uri / Security
fast-uri vulnerable to server-side request forgery via malformed IPv6 normalization
Affected releases · fast-uri
- 4.x4.0.0 – 4.1.2Fixed in 4.1.3
- 3.x3.0.0 – 3.1.5Fixed in 3.1.6
- 2.x2.3.1 – 2.4.4Fixed in 2.4.5
On 4.x, the newest line:
npm install fast-uri@4.1.3Every release on a timeline
Affected
4.0.0 – 4.1.2
5 releases
Fixed
4.1.3 – 4.2.3
7 releases, latest
Affected
3.0.0 – 3.1.5
13 releases
Fixed
3.1.6 – 3.1.9
4 releases
Not affected
2.0.0 – 2.3.0
4 releases
Affected
2.3.1 – 2.4.4
6 releases
Fixed
2.4.5 – 2.4.8
4 releases
What happens
Impact
fast-uri does not validate the complete RFC 3986 grammar for bracketed IPv6 literals, so a malformed literal with invalid trailing text is silently truncated to a different valid IPv6 address with no error reported. For example, normalize('http://[::not-valid]/private') returns http://[::]/private, and [fc00::not-hex] and [fe80::not-hex] collapse to [fc00::] and [fe80::]. An application that normalizes an untrusted URL before an outbound request, redirect, or host-policy check can be routed to a local or private address such as loopback (::1), unique-local, or link-local. Because parse().error is unset for these inputs, checking it does not protect the consumer.
Patches
Upgrade to fast-uri 2.4.5, 3.1.6, or 4.1.3. Malformed IPv6 literals are now rejected with a host error instead of being normalized to a valid address.
Workarounds
Reject untrusted URLs whose host is a bracketed IPv6 literal before passing them to fast-uri, or route outbound requests against an explicit allowlist of addresses rather than trusting the normalized host.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.