webcrack présente une vulnérabilité d'écriture de fichier arbitraire sur Windows lors de l'analyse et de la sauvegarde d'un Bundle malveillant

The primary impact of CVE-2024-43373 is the potential for arbitrary file overwrites on a Windows system. An attacker could leverage this vulnerability to modify critical system files, install malware, or gain persistent access to the compromised machine. The vulnerability arises from insufficient input validation when processing file paths during the unpack bundles and saving operations. By injecting path traversal sequences (e.g., ../) into the module name, an attacker can bypass security checks and write files to arbitrary locations. This could lead to complete system compromise, depending on the permissions of the process running webcrack.

Organizations and developers using the webcrack Node.js package in their applications, particularly those deploying on Windows systems, are at risk. This includes developers integrating webcrack into custom tools or applications, and those relying on webcrack within larger Node.js projects. Shared hosting environments where multiple users share the same server are also at increased risk if one user's application is compromised.

• nodejs / server:

find / -name "webcrack" -type d -print0 | xargs -0 ls -l

• nodejs / server:

ps aux | grep webcrack

• generic web: Inspect web server access logs for requests containing suspicious file paths or path traversal sequences (e.g., ../). • generic web: Review web application code for any instances where user-supplied input is used to construct file paths without proper sanitization.

1. 2024-08-14Disclosure

   disclosure

1. Réservé2024-08-09
2. Publiée2024-08-14
3. Modifiée2024-11-18
4. EPSS mis à jour2026-04-02

The primary mitigation for CVE-2024-43373 is to upgrade to webcrack version 2.14.1 or later, which includes the necessary fix. If upgrading immediately is not feasible, consider implementing temporary workarounds. Restrict the execution of webcrack to a sandboxed environment with limited file system access. Implement strict input validation on all file paths processed by the unpack bundles and saving features, ensuring that path traversal sequences are properly sanitized. Monitor system logs for suspicious file modification activity, particularly in sensitive directories. Consider using a Web Application Firewall (WAF) to filter out malicious requests containing path traversal attempts.