Babel Preset Stage 2 offers a convenient collection of Babel plugins that implement JavaScript features currently in stage 2 of the TC39 standardization process, making it easier for developers to experiment with upcoming language enhancements. Comparing version 6.11.0 to its predecessor, 6.5.0, reveals a subtle but important change in the included plugins and dependency versions.
The update from 6.5.0 to 6.11.0 primarily involves an update to the babel-preset-stage-3 dependency, moving from a constraint satisfied by ^6.3.13 in the older version to ^6.11.0 in the newer one. Most crucially, the babel-plugin-syntax-trailing-function-commas plugin, present as a direct dependency in version 6.5.0, is *removed* in version 6.11.0.
This suggests that the functionality provided by babel-plugin-syntax-trailing-function-commas was likely incorporated into a later version of babel-preset-stage-3 or another plugin included indirectly via the updated babel-preset-stage-3 dependency. Developers upgrading should be aware of this change and ensure their code continues to function as expected. The inclusion of babel-plugin-transform-object-rest-spread remains consistent across both versions, indicating continued support for object rest and spread properties. Both versions are MIT licensed and maintained within the Babel project. Given the release dates, 6.11.0 offers benefits of latest stage 3 features as of June 2016, while 6.5.0 represents the features available in February 2016. Therefore, prefer using the latest version.
All the vulnerabilities related to the version 6.11.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