Packages / fast-uri / Security
fast-uri vulnerable to improper path equivalence in relative reference normalization
Affected releases · fast-uri
- 4.x4.0.0 – 4.2.2Fixed in 4.2.3
- 3.x3.0.0 – 3.1.8Fixed in 3.1.9
- 2.x2.0.0 – 2.4.7Fixed in 2.4.8
- 1.x and older0.0.1 – 1.0.1No fix, no longer updated
On 4.x, the newest line:
npm install fast-uri@4.2.3Every release on a timeline
Affected
4.0.0 – 4.2.2
11 releases
Fixed
4.2.3
1 release, latest
Affected
3.0.0 – 3.1.8
16 releases
Fixed
3.1.9
1 release
Affected
2.0.0 – 2.4.7
13 releases
Fixed
2.4.8
1 release
Affected
1.0.0 – 1.0.1
2 releases
Affected
0.0.1 – 0.0.2
2 releases
What happens
Impact
fast-uri's normalize() and serialize() apply RFC 3986 dot-segment removal (remove_dot_segments) to the path of a relative-path reference. RFC 3986 section 5.2.4 defines that algorithm only for the merged target path during resolution, not for the reference itself, so applied to the reference it drops leading .. segments and can turn a document-relative reference into a root-relative one.
For example, normalize('a/../b') returns /b and normalize('../x') returns x, so resolve(base, normalize(ref)) points at a different resource than resolve(base, ref), and equal() treats distinct references as the same.
Applications that normalize attacker-supplied or user-supplied relative references and then resolve them, or use them as cache, deduplication, or authorization keys, can have a reference escape its intended directory and point at a different resource.
Patches
Upgrade to fast-uri 2.4.8, 3.1.9, or 4.2.3.
Workarounds
Do not normalize a relative reference before resolving it. Resolve it against the absolute base first, then normalize the absolute 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.