Babel Preset Stage 2 streamlines the integration of ECMAScript stage 2 features into your JavaScript projects, offering a balance between experimental functionality and relative stability. Version 6.17.0, released on October 1, 2016, builds upon the foundation laid by version 6.16.0, released just days prior on September 28, 2016. Developers upgrading to 6.17.0 from 6.16.0 will notice a streamlined dependency structure. Specifically, version 6.17.0 removes direct dependencies on babel-plugin-transform-object-rest-spread and babel-plugin-transform-async-generator-functions. These features are now implicitly included via the updated dependency on babel-preset-stage-3 at version ^6.17.0.
The key difference lies in how stage 2 features are managed. In version 6.16.0, Stage 2 explicitly declared babel-plugin-transform-object-rest-spread and babel-plugin-transform-async-generator-functions. In version 6.17.0, it delegates these features to babel-preset-stage-3. This structural shift helps to simplify the preset's configuration and promotes a clearer separation of concerns between feature stages. For developers, this update means a cleaner configuration by relying on babel-preset-stage-3 to handle functionalities related to object rest/spread properties and async generator functions. While the end result in terms of transpiled code remains largely the same, the updated dependency management offers a more maintainable and organized approach to incorporating experimental JavaScript features using Babel.
All the vulnerabilities related to the version 6.17.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-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