Packages / fast-uri / Security
fast-uri vulnerable to host confusion via unchecked WHATWG host canonicalization
Affected releases · fast-uri
- 4.x4.0.1 – 4.2.2Fixed in 4.2.3
- 3.x3.1.3 – 3.1.8Fixed in 3.1.9
- 2.x2.4.2 – 2.4.7Fixed in 2.4.8
On 4.x, the newest line:
npm install fast-uri@4.2.3Every release on a timeline
Not affected
4.0.0
1 release
Affected
4.0.1 – 4.2.2
10 releases
Fixed
4.2.3
1 release, latest
Not affected
3.0.0 – 3.1.2
10 releases
Affected
3.1.3 – 3.1.8
6 releases
Fixed
3.1.9
1 release
Not affected
2.0.0 – 2.4.1
7 releases
Affected
2.4.2 – 2.4.7
6 releases
Fixed
2.4.8
1 release
What happens
Impact
fast-uri versions >= 2.4.2, <= 2.4.7, >= 3.1.3, <= 3.1.8, and >= 4.0.1, <= 4.2.2 can silently rewrite the host of an HTTP-family URL (http, https, ws, wss, or any scheme with domainHost: true). For those schemes canonicalizeHost() passes the parsed host to the WHATWG URL parser and adopts its .hostname without checking that the parser read the whole input as a host. RFC 3986 permits @ inside the host group and the WHATWG parser strips TAB, LF, and CR, so the authority fast-uri reports is rewritten by that second parser with no error set: data before an @ is dropped and whitespace is removed.
For example, fast-uri parses http://a@b@evil.example/ to host evil.example (dropping the b segment), and a host containing a raw TAB, CR, or LF has those characters stripped. equal() then treats a whitespace-smuggled host as the same as the clean one, and resolve() rewrites the authority the same way.
Applications that use fast-uri to enforce host-based policy (denylists, loopback filtering, redirect validation, outbound proxy routing) on one representation, such as the raw input, see a policy/use desync: the canonical host fast-uri returns differs from what was checked, and traffic can be steered to an unintended destination.
Patches
Upgrade to fast-uri 2.4.8, 3.1.9, or 4.2.3.
Workarounds
Reject URIs whose authority contains more than one @, or contains TAB, CR, or LF, before calling fast-uri. Alternatively, treat any non-empty parse(x).error as fatal, and compare hosts only from the same parse() result.
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.