Babel-preset-env is a powerful tool that allows developers to use the latest JavaScript features while ensuring compatibility with various target environments. Versions 1.7.0 and 1.6.1 share a core purpose and many dependencies, but some key differences make the newer version a worthwhile upgrade. Both versions smartly manage JavaScript transformations based on specified browser or environment targets, streamlining the process of supporting diverse platforms.
The most notable change lies within the browserslist dependency. Version 1.7.0 uses browserslist version ^3.2.6, while version 1.6.1 relies on ^2.1.2. This update improves browser targeting capabilities. Browserslist is what allows babel-preset-env to transform only the necessary code. The rest of the dependencies instead are the same.
Although most of the dev dependencies are the same, the updated browserslist offers enhanced configuration options and improved accuracy in identifying target browsers. In essence, upgrading to version 1.7.0 equips you with a more refined and precise mechanism for managing JavaScript compatibility, with minimal impact on your development workflow.
All the vulnerabilities related to the version 1.7.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