Babel Preset Stage 2 simplifies the process of incorporating ECMAScript Stage 2 features into your JavaScript projects. These features are candidates for future standardization, offering developers early access to innovative functionalities. Comparing versions 6.2.4 and 6.3.13 highlights subtle but potentially important distinctions. Both versions, licensed under MIT, are authored by Sebastian McKenzie and pull dependencies from the same core Babel ecosystem, notably babel-preset-stage-3, babel-plugin-transform-object-rest-spread, and babel-plugin-syntax-trailing-function-commas.
The key difference lies in the versions of these dependencies. Version 6.3.13 utilizes newer iterations of its dependencies (specifically ^6.3.13), while 6.2.4 relies on older versions (^6.2.4). This subtle shift implies that version 6.3.13 includes bug fixes, performance enhancements, and potentially new features introduced within those dependent packages between these versions.
Importantly, the release dates also differ, with 6.3.13 released on December 4, 2015, and 6.2.4 on November 25, 2015. Therefore upgrading from version 6.2.4 to 6.3.13 ensures you are benefitting from the latest compatible features and bugfixes in stage 2 proposals. Developers should check the changelogs of babel-preset-stage-3, babel-plugin-transform-object-rest-spread, and babel-plugin-syntax-trailing-function-commas to understand the specific changes introduced in the newer versions, and assess if they are relevant or breaking for their projects, before upgrading.
All the vulnerabilities related to the version 6.3.13 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