Debian LinuxOperating system · Debian
CVE-2023-45133
A fix is available.
Upgrade to 0.4.3 / 0.4.6 or later.
See remediation →
90/100
Remediation priority · Urgent
Zero-click
Patch available
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBabel is a compiler for writingJavaScript. In `@babel/traverse` prior to versions 7.23.2 and 8.0.0-alpha.4 and all versions of `babel-traverse`, using Babel to compile code that was specifically crafted by an attacker can lead to arbitrary code execution during compilation, when using plugins that rely on the `path.evaluate()`or `path.evaluateTruthy()` internal Babel methods. Known affected plugins are `@babel/plugin-transform-runtime`; `@babel/preset-env` when using its `useBuiltIns` option; and any "polyfill provider" plugin that depends on `@babel/helper-define-polyfill-provider`, such as `babel-plugin-polyfill-corejs3`, `babel-plugin-polyfill-corejs2`, `babel-plugin-polyfill-es-shims`, `babel-plugin-polyfill-regenerator`. No other plugins under the `@babel/` namespace are impacted, but third-party plugins might be. Users that only compile trusted code are not impacted. The vulnerability has been fixed in `@babel/[email protected]` and `@babel/[email protected]`. Those who cannot upgrade `@babel/traverse` and are using one of the affected packages mentioned above should upgrade them to their latest version to avoid triggering the vulnerable code path in affected `@babel/traverse` versions: `@babel/plugin-transform-runtime` v7.23.2, `@babel/preset-env` v7.23.2, `@babel/helper-define-polyfill-provider` v0.4.3, `babel-plugin-polyfill-corejs2` v0.4.6, `babel-plugin-polyfill-corejs3` v0.8.5, `babel-plugin-polyfill-es-shims` v0.10.0, `babel-plugin-polyfill-regenerator` v0.5.3.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisA detailed technical summary for this CVE is being prepared.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Debian LinuxOperating system
Affected:
= 10.0= 11.0= 12.0
BabelApplication
Affected:
< 7.23.2= 8.0.0
Babel Helper Define Polyfill ProviderApplication
Affected:
< 0.4.3
Babel Plugin Polyfill Corejs2Plugin / extension
Affected:
< 0.4.6
Babel Plugin Polyfill Corejs3Plugin / extension
Affected:
< 0.8.5
Babel Plugin Polyfill Es ShimsPlugin / extension
Affected:
< 0.10.0
Babel Plugin Polyfill RegeneratorPlugin / extension
Affected:
< 0.5.3
Babel Plugin Transform RuntimePlugin / extension
Affected:
< 7.23.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped
Upgrade available
Upgrade to 0.4.3 / 0.4.6 / 0.5.3 or later
Fixed in
0.4.30.4.60.5.3
Vendor patch
github.com →
Recommended fix
High confidence
@babel/[email protected] (or @babel/[email protected] for Babel 8)
- Upgrade @babel/traverse to version 7.23.2 or later (or 8.0.0-alpha.4 or later for Babel 8)
- If using @babel/plugin-transform-runtime, upgrade to v7.23.2 or later
- If using @babel/preset-env with the useBuiltIns option, upgrade to v7.23.2 or later
- If using @babel/helper-define-polyfill-provider, upgrade to v0.4.3 or later
- If using babel-plugin-polyfill-corejs2, upgrade to v0.4.6 or later
- If using babel-plugin-polyfill-corejs3, upgrade to v0.8.5 or later
- If using babel-plugin-polyfill-es-shims, upgrade to v0.10.0 or later
- If using babel-plugin-polyfill-regenerator, upgrade to v0.5.3 or later
Caveat Minimal - this is a security patch upgrade; however, review the @babel/traverse 7.23.2 and 8.0.0-alpha.4 changelogs for any potential breaking changes in your specific usage
Generated from the published advisory — verify against the referenced sources before acting.
We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950.
Get the upgrade done
Scan for this in your stack
Free · runs locally
dbcve dependency scanner
Check whether your project pulls in CVE-2023-45133 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-45133 in production — separate from our analysis above.
Know something about CVE-2023-45133?
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
What this is
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
What belongs here
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data