Babel Preset Stage 1 is a collection of Babel plugins used to enable ECMAScript features that are currently at stage 1 of the TC39 standardization process. Comparing versions 6.16.0 and 6.22.0, developers will notice key differences in the dependency versions. Notably, babel-plugin-transform-class-constructor-call and babel-plugin-transform-export-extensions were updated from ^6.3.13 to ^6.22.0. This suggests bug fixes, performance improvements, or adherence to newer specifications within these specific transform plugins. Moreover, babel-preset-stage-2 was updated from ^6.16.0 to ^6.22.0, meaning that developers will automatically benefit from the updated features and fixes in the Stage 2 functionalities, ensuring better compatibility and stability with evolving JavaScript standards. The release dates also indicate that version 6.22.0 was released significantly later (January 2017) compared to version 6.16.0 (September 2016), consolidating several months of improvements and potentially addressing reported issues. Using Stage 1 presets allows developers to experiment with upcoming JavaScript features early in their projects, providing a glimpse into the future of the language and enabling the adoption of cutting-edge functionalities. However, note that Stage 1 features are subject to change and may not be finalized, calling for an awareness of potential versioning implications.
All the vulnerabilities related to the version 6.22.0 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-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/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