Babel Preset Stage 0 is a collection of Babel plugins that enable experimental JavaScript features still in the early stages of proposal within the ECMAScript standards process. Comparing versions 6.1.2 and 6.1.17, the primary difference lies in the updated dependencies. Version 6.1.17 includes "^6.1.17" versions of babel-plugin-transform-do-expressions and babel-plugin-transform-function-bind, and babel-preset-stage-1, while version 6.1.2 relies on older "^6.0.14" versions for the plugins and "^6.1.2" for babel-preset-stage-1. This signifies an upgrade in the underlying transformation capabilities for these specific experimental features.
For developers, opting for version 6.1.17 ensures access to the latest bug fixes, performance improvements, and potentially refined implementations of "do-expressions" and "function-bind" transformations. Utilizing Stage 0 presets allows developers to experiment with bleeding-edge JavaScript syntax and functionalities before they are finalized, enabling early adoption and feedback. However, it's crucial to acknowledge that Stage 0 features are subject to change or removal as the ECMAScript standardization process evolves. Therefore, using this preset requires careful consideration and may not be suitable for production environments demanding long-term stability. The upgrade to 6.1.17 provides the newer versions of the dependencies and their bug fixes so it's a good choice.
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