Babel-preset-stage-2 is an npm package designed to simplify the use of Babel plugins that implement features at stage 2 of the TC39 standardization process for ECMAScript. It acts as a convenient preset, bundling together commonly used plugins to enable cutting-edge JavaScript syntax transformations. Examining versions 6.0.14 and 6.0.15, we see a subtle but important update. Both versions include dependencies on babel-preset-stage-3, babel-plugin-transform-object-rest-spread, and babel-plugin-syntax-trailing-function-commas, all essential for stage 2 functionality. However, the key difference lies in their release dates and the version of their dependencies. Version 6.0.15 was released on November 1, 2015, slightly after version 6.0.14, released on October 30, 2015.
While on the surface version 6.0.15 might appear as a minor iteration, the update indicates a potential roll-out or bug fix within the babel ecosystem. Developers using babel-preset-stage-2 should always aim to use the latest stable version, currently 6.0.15 at the time according to the data, to ensure they're benefiting from the most recent improvements and bug fixes within the preset and its dependencies. Keeping abreast of these minor version bumps within babel presets ensures project alignement with evolving JavaScript standards and helps to maintain code compatibility across different environments. The babel-preset-stage-3 dependency version differences indicate that this is propably the most relevant upgrade.
All the vulnerabilities related to the version 6.0.15 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