Packages / fast-uri / Security
fast-uri vulnerable to host confusion via percent-encoded authority delimiters
Affected releases · fast-uri
- 3.x3.0.0 – 3.1.1Fixed in 3.1.2
- 2.x2.0.0 – 2.4.0Fixed in 2.4.1
- 1.x and older0.0.1 – 1.0.1No fix, no longer updated
On 3.x, the newest line:
npm install fast-uri@3.1.2Every release on a timeline
Not affected
4.0.0 – 4.2.3
12 releases, latest
Affected
3.0.0 – 3.1.1
9 releases
Fixed
3.1.2 – 3.1.9
8 releases
Affected
2.0.0 – 2.4.0
6 releases
Fixed
2.4.1 – 2.4.8
8 releases
Affected
1.0.0 – 1.0.1
2 releases
Affected
0.0.1 – 0.0.2
2 releases
What happens
Impact
fast-uri v3.1.1 and earlier decodes percent-encoded authority delimiters (%40 as @, %3A as :) inside the host component and serializes them back as raw characters. This changes the URI structure, turning a hostname into userinfo plus a different host.
For example, http://trusted.com%40evil.com/ normalizes to http://trusted.com@evil.com/, which reparses as host evil.com with userinfo trusted.com.
Applications that normalize untrusted URLs before host allowlist checks, redirect validation, or outbound request routing can be steered to a different authority than the original URL appeared to contain.
Patches
Upgrade to fast-uri >= 3.1.2, or if you are in the v2.x release line, v2.4.1
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.