webpack-dev-middleware
Affected
- introduced
7.0.0, fixed7.1.0(semver)
Fixed versions
7.1.0
Fix
- Fixed version
7.1.0npm install [email protected]
Advisory
Also known as: CVE-2024-29180
Path traversal in webpack-dev-middleware
Summary
_The webpack-dev-middleware middleware does not validate the supplied URL address sufficiently before returning the local file. It is possible to access any file on the developer's machine._
Details
The middleware can either work with the physical filesystem when reading the files or it can use a virtualized in-memory _memfs_ filesystem.
If _writeToDisk_ configuration option is set to true, the physical filesystem is used:
https://github.com/webpack/webpack-dev-middleware/blob/7ed24e0b9f53ad1562343f9f517f0f0ad2a70377/src/utils/setupOutputFileSystem.js#L21
The _getFilenameFromUrl_ method is used to parse URL and build the local file path.
The public path prefix is stripped from the URL, and the unsecaped path suffix is appended to the _outputPath_:
https://github.com/webpack/webpack-dev-middleware/blob/7ed24e0b9f53ad1562343f9f517f0f0ad2a70377/src/utils/getFilenameFromUrl.js#L82
As the URL is not unescaped and normalized automatically before calling the midlleware, it is possible to use _%2e_ and _%2f_ sequences to perform path traversal attack.
PoC
_A blank project can be created containing the following configuration file webpack.config.js:_
`module.exports = {
devServer: {
devMiddleware: {
writeToDisk: true
}
}
};
`
When started, it is possible to access any local file, e.g. _/etc/passwd_:$ curl localhost:8080/public/..%2f..%2f..%2f..%2f../etc/passwd
root:x:0:0:root:/root:/bin/bash
daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
bin:x:2:2:bin:/bin:/usr/sbin/nologin
sys:x:3:3:sys:/dev:/usr/sbin/nologin
sync:x:4:65534:sync:/bin:/bin/sync
games:x:5:60:games:/usr/games:/usr/sbin/nologin
Impact
The developers using _webpack-dev-server_ or _webpack-dev-middleware_ are affected by the issue. When the project is started, an attacker might access any file on the developer's machine and exfiltrate the content (e.g. password, configuration files, private source code, ...).
If the development server is listening on a public IP address (or 0.0.0.0), an attacker on the local network can access the local files without any interaction from the victim (direct connection to the port).
If the server allows access from third-party domains (CORS, **_Allow-Access-Origin: *_** ), an attacker can send a malicious link to the victim. When visited, the client side script can connect to the local server and exfiltrate the local files.
Recommendation
The URL should be unescaped and normalized before any further processing.
High Basis: The source's own band: HIGH
7.0.0, fixed 7.1.0 (semver)7.1.0
7.1.0npm install [email protected]6.0.0, fixed 6.1.2 (semver)6.1.2
6.1.2npm install [email protected]0, fixed 5.3.4 (semver)5.3.4
5.3.4npm 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