Babel preset stage-2, a collection of Babel plugins enabling ECMAScript features in the stage 2 draft proposal, saw a notable update from version 6.22.0 to 6.24.1. This upgrade primarily involved dependency updates across its core plugins. Specifically, babel-preset-stage-3, babel-plugin-transform-decorators, and babel-plugin-transform-class-properties all advanced from version 6.22.0 to 6.24.1. The babel-plugin-syntax-dynamic-import remained unchanged at version 6.18.0.
For developers utilizing this preset, the key takeaway is the alignment with newer iterations of the included stage 3 plugins and the decorators and class properties transforms. These upgrades likely incorporated bug fixes, performance enhancements, and potentially new features or adherence to evolving specifications within the respective ECMAScript proposals. Maintaining up-to-date dependencies ensures compatibility with the latest language features and best practices. Version 6.24.1 offers a more current configuration for developers leveraging stage 2 features in their JavaScript projects.
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