Babel Preset Stage 1 is a collection of Babel plugins designed to enable ECMAScript features that are in stage 1 of the TC39 standardization process. This preset allows developers to experiment with cutting-edge JavaScript proposals before they are finalized, enhancing their code with future syntax and functionalities. Comparing version 6.1.17 with the previous stable version 6.1.2, there are several notable changes focused on dependency updates.
Specifically, version 6.1.17 upgrades its core plugin dependencies, including babel-plugin-transform-class-constructor-call, babel-plugin-transform-class-properties, babel-plugin-transform-decorators, and babel-plugin-transform-export-extensions to version ^6.1.17. This indicates a consolidation and alignment of these plugins. Previously, in version 6.1.2, these plugins relied on versions from the ^6.0.14 and ^6.0.15 ranges. Another important improvement is the dependency update of babel-preset-stage-2 to ^6.1.17 to maintain better compatibility and utilize the latest features included within Stage 2 proposals. These updates likely incorporate bug fixes, performance improvements, and alignment with the evolving ECMAScript standards.
For developers considering using Babel Preset Stage 1, these updates are essential to ensure they are leveraging the most recent and reliable implementations of stage 1 features. Upgrading to version 6.1.17 offers a more consistent and up-to-date compilation environment for experimental JavaScript code.
All the vulnerabilities related to the version 6.1.17 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