CVE-2022-37599 — loader-utils
HIGHCVE-2022-37599 is a high-severity (CVSS 7.5) CWE-1333 vulnerability in loader-utils. A fix is available for loader-utils — see the affected versions and patch details below.
loader-utils is vulnerable to Regular Expression Denial of Service (ReDoS)
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-2022-37599 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 376,715 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.
loader-utilsnpmDescription
A Regular expression denial of service (ReDoS) flaw was found in Function interpolateName in interpolateName.js in webpack loader-utils 2.0.0 via the resourcePath variable in interpolateName.js.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | loader-utils | ≥ 1.0.0&&< 1.4.2 | 1.4.2npm install loader-utils@1.4.2 |
| 📦npm | loader-utils | ≥ 2.0.0&&< 2.0.4 | 2.0.4npm install loader-utils@2.0.4 |
| 📦npm | loader-utils | ≥ 3.0.0&&< 3.2.1 | 3.2.1npm install loader-utils@3.2.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for loader-utils, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update loader-utils to 1.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-37599 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-2022-37599 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-37599. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
In Red Hat OpenShift Logging the openshift-logging/kibana6-rhel8 container and openshift-logging/logging-view-plugin-rhel8 bundles many nodejs packages as a build time dependencies, including loader-utils package. The vulnerable code is not used hence the impact to OpenShift Logging by this vulnerability is Low.
| Product | Fixed in | Advisory |
|---|---|---|
| RHPAM 7.13.4 async | loader-utils | RHSA-2023:4983 |
Frequently Asked Questions
Is CVE-2022-37599 in your dependencies?
O3 Security finds CVE-2022-37599 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.