Babel Preset Stage 1 is a collection of Babel plugins designed to enable experimental ECMAScript features that are currently in Stage 1 of the TC39 standardization process. This preset allows developers to start using these cutting-edge features in their codebases, providing a glimpse into the future of JavaScript. Examining versions 6.1.2 and 6.0.15 reveals subtle but important updates. Both versions include essential transforms like class constructor calls, class properties, decorators, and export extensions, all crucial for modern JavaScript development.
The key difference lies in the version of babel-preset-stage-2 they depend on. Version 6.1.2 utilizes babel-preset-stage-2 version 6.1.2 as well, whereas the older 6.0.15 relies on version 6.0.15 of the same dependency. This seemingly small change reflects improvements and bug fixes within the Stage 2 featureset and ensures compatibility between the Stage 1 and Stage 2 features. Consequently, upgrading to version 6.1.2 ensures you benefit from the latest advancements within Stage 2, minimizing potential conflicts and maximizing the stability of your experimental features.
For developers aiming to stay on the bleeding edge and experiment with upcoming JavaScript features, Babel Preset Stage 1 provides a valuable tool. When migrating between versions of babel-preset-stage-1, be sure to check the changelogs for both babel-preset-stage-1 and babel-preset-stage-2, to ensure that you are up to date on any breaking changes or new features.
All the vulnerabilities related to the version 6.1.2 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