Babel preset stage-1 offers a convenient way for developers to incorporate features and syntax proposals that are in stage 1 of the TC39 standardization process into their JavaScript projects. Comparing version 6.16.0 with the earlier stable version 6.13.0, the key difference lies in the updated dependency on babel-preset-stage-2. Version 6.16.0 relies on babel-preset-stage-2 version 6.16.0, while the older version depends on babel-preset-stage-2 version 6.13.0. This update in the stage-2 preset likely incorporates new features, bug fixes, and performance improvements relevant to stage 2 proposals. Developers using babel-preset-stage-1 should take note of this dependency update, as it dictates the specific set of stage 2 features included in their build process. Keep in mind that stage 1 features are experimental and subject to change, potentially introducing breaking changes in future Babel updates as the JavaScript language evolves. Checking the changelogs for both babel-preset-stage-1 and babel-preset-stage-2 around the release date 2016-09-28 is highly advisable to understand the precise changes and assess any potential impact on your project. This preset, like others in the Babel ecosystem, are MIT licensed and were maintaned by Sebastian McKenzie during the period in study.
All the vulnerabilities related to the version 6.16.0 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