Babel-preset-stage-1 is a valuable tool for developers aiming to leverage JavaScript features still under consideration for standardization. This preset packages together a selection of Babel plugins, enabling support for ECMAScript proposals currently at stage 1. Comparing version 6.0.15 with its predecessor, 6.0.14, reveals subtle yet important differences primarily in dependency versioning.
Specifically, version 6.0.15 updates its dependencies to align with the latest available releases at the time. While the core plugins like babel-plugin-transform-class-constructor-call, babel-plugin-transform-class-properties, babel-plugin-transform-decorators, and babel-plugin-transform-export-extensions see minor version bumps, the crucial babel-preset-stage-2 dependency is also updated. This ensures compatibility and takes advantage of any bug fixes or performance improvements introduced in those dependent packages.
For developers, this means that upgrading to version 6.0.15 provides a more stable and potentially performant environment for experimenting with stage 1 features. While the underlying language features supported remain consistent across both versions, the updated dependencies provide the assurance that you're utilizing the most recent and refined implementations of these transforms. Keep in mind that stage 1 features are still subject to change, so this preset is best suited for experimental projects or for developers comfortable with potential breaking changes as the JavaScript language evolves.
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