Prior to versions 7.1.0, 6.1.2, and 5.3.4, the webpack-dev-middleware development middleware for devpack 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. 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. 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`. 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. 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. 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, 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. Starting with fixed versions 7.1.0, 6.1.2, and 5.3.4, the URL is unescaped and normalized before any further processing.

The version of Tencent Linux installed on the remote TencentOS Server 4 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the TSSA-2025:0213 advisory.

    Package updates are available for TencentOS Server 4 that fix the following vulnerabilities:

    CVE-2024-29180:
    Prior to versions 7.1.0, 6.1.2, and 5.3.4, the webpack-dev-middleware development middleware for devpack     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. 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. 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`. 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.

    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. 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, 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. Starting with fixed versions 7.1.0, 6.1.2, and 5.3.4, the URL is unescaped and normalized before     any further processing.

Tenable has extracted the preceding description block directly from the Tencent Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - Prior to versions 7.1.0, 6.1.2, and 5.3.4, the webpack-dev-middleware development middleware for devpack
    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. 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. 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`. 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. 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. 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, 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. Starting with fixed versions 7.1.0, 6.1.2, and 5.3.4, the URL is unescaped and
    normalized before any further processing. (CVE-2024-29180)

ID	Name	Product	Family	Severity
276127	TencentOS Server 4: pcs (TSSA-2025:0213)	Nessus	Tencent Local Security Checks	high
420087	SCA: security update for webpack-dev-middleware (GHSA-wr3j-pwj9-hqq6)	Tenable Cloud Security	SCA Checks	high
420087	SCA: security update for webpack-dev-middleware (GHSA-wr3j-pwj9-hqq6)	Tenable Self-Hosted Container Security	SCA Checks	high

Detections

Analytics

CVE-2024-29180

high

Tenable Plugins

high

high

high