Babel-preset-stage-1 offers a convenient configuration for Babel, streamlining the integration of JavaScript features proposed at Stage 1 of the TC39 standardization process. These features are considered for inclusion in future JavaScript versions, allowing developers to experiment with cutting-edge syntax and functionalities. Compared to version 6.22.0, version 6.24.1 introduces updates across its dependencies. Specifically, babel-plugin-transform-class-constructor-call and babel-preset-stage-2 are upgraded to version 6.24.1 alongside the preset itself. This synchronization of dependencies ensures that developers benefit from the latest bug fixes, performance improvements, and feature enhancements within those individual components. Developers should note the updated version dependencies as this may include breaking changes, which although unlikely, it is good to keep in mind before upgrading.
While the core functionality of enabling Stage 1 features remains consistent, the updated dependencies within version 6.24.1 provide a more robust and refined experience for developers leveraging experimental JavaScript features. The babel-plugin-transform-export-extensions dependency remains at version 6.22.0, indicating stability and continued compatibility. Check for compatibility to avoid introducing unexpected behavior in their projects. For developers aiming to stay current with the bleeding edge of JavaScript development, upgrading to version 6.24.1 offers access to the most recent iterations of the Stage 1 proposal implementations within the Babel ecosystem.
All the vulnerabilities related to the version 6.24.1 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