Babel preset stage 0, a tool designed to empower developers with cutting-edge JavaScript features, underwent a subtle but notable update from version 6.0.14 to 6.0.15. Both versions serve the same core purpose: bundling plugins that enable experimental JavaScript features still in Stage 0 of the TC39 standardization process. This provides developers an opportunity to experiment with bleeding-edge syntax and functionality before they become widely adopted.
The distinction lies primarily in the dependency on babel-preset-stage-1. Version 6.0.15 upgraded this dependency to ^6.0.15 from ^6.0.14 in the prior version. This change signifies an alignment with the latest features and bug fixes present in the Stage 1 preset. While the underlying plugins for do-expressions and function binding remain consistent between the two versions, opting for version 6.0.15 ensures compatibility and access to the most recent improvements within the broader Babel ecosystem. Developers leveraging Babel preset stage 0 should carefully examine this dependency update, ensure its compatibility, particularly with existing project configurations, and update accordingly to enjoy the latest advancements in experimental JavaScript transformations. The upgrade provides access to the newest features trickling down in the Javascript landscape.
All the vulnerabilities related to the version 6.0.15 of the package
Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code
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@babel/helper-define-polyfill-provider, such as babel-plugin-polyfill-corejs3, babel-plugin-polyfill-corejs2, babel-plugin-polyfill-es-shims, babel-plugin-polyfill-regeneratorNo 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/traverse@7.23.2.
Babel 6 does not receive security fixes anymore (see Babel's security policy), hence there is no patch planned for babel-traverse@6.
@babel/traverse to v7.23.2 or higher. You can do this by deleting it from your package manager's lockfile and re-installing the dependencies. @babel/core >=7.23.2 will automatically pull in a non-vulnerable version.@babel/traverse and are using one of the affected packages mentioned above, 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.3babel-plugin-polyfill-corejs2 v0.4.6babel-plugin-polyfill-corejs3 v0.8.5babel-plugin-polyfill-es-shims v0.10.0babel-plugin-polyfill-regenerator v0.5.3