Babel Preset Stage 0 is a valuable tool for developers eager to experiment with cutting-edge JavaScript features still in the early stages of proposal. Versions 6.2.4 and 6.1.18 both serve this purpose, offering a curated collection of Babel plugins that transform your code, enabling you to use future syntax today. The key change moving from version 6.1.18 to 6.2.4 involves dependency updates. Both versions bundle babel-plugin-transform-do-expressions, babel-plugin-transform-function-bind, and babel-preset-stage-1, but version 6.2.4 upgrades these dependencies to their respective ^6.2.4 versions, while the older version uses ^6.1.18.
This update is essential for developers who want to stay current with the latest iterations of stage 0 proposals and bug fixes within those plugins. While the core functionality remains consistent – allowing early adoption of features like do-expressions and function binding syntax – using the newer version ensures compatibility with other Babel packages and reduces the risk of encountering deprecated features. Developers should always consult the related Babel plugin documentation for detailed information on specific features. Consider upgrading to version 6.2.4 for a more robust and up-to-date experience with experimental JavaScript.
All the vulnerabilities related to the version 6.2.4 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