Packages / fast-uri / Security
fast-uri vulnerable to host confusion via failed IDN canonicalization
Affected releases · fast-uri
- 4.x4.0.0Fixed in 4.0.1
- 3.x3.0.0 – 3.1.2Fixed in 3.1.3
- 2.x2.3.1 – 2.4.1Fixed in 2.4.2
On 4.x, the newest line:
npm install fast-uri@4.0.1Every release on a timeline
Affected
4.0.0
1 release
Fixed
4.0.1 – 4.2.3
11 releases, latest
Affected
3.0.0 – 3.1.2
10 releases
Fixed
3.1.3 – 3.1.9
7 releases
Not affected
2.0.0 – 2.3.0
4 releases
Affected
2.3.1 – 2.4.1
3 releases
Fixed
2.4.2 – 2.4.8
7 releases
What happens
Impact
fast-uri versions >= 2.3.1, <= 4.0.0 fail to canonicalize Unicode/IDN hostnames for HTTP-family URLs. The IDN conversion path calls URL.domainToASCII(...) on the global WHATWG URL constructor, where that helper does not exist. The resulting TypeError is silently routed into parsed.error, but parse(), normalize(), and equal() all return with the host left in its original Unicode form.
For example, http://127。0。0。1/ is treated by fast-uri as host 127。0。0。1, while Node's WHATWG URL parser and fetch() canonicalize the same input to 127.0.0.1.
Applications that use fast-uri to enforce host-based policy (denylists, loopback filtering, redirect validation, outbound proxy routing) before passing the same URL into Node's URL or fetch() consumers see a policy/use desync and can be steered to an unintended destination.
Patches
Upgrade to fast-uri v4.0.1, v3.1.3, or v2.4.2
Workarounds
None. Upgrade to the patched version.
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.