Babel-preset-env is a powerful tool designed to simplify Babel configuration, allowing developers to easily target specific JavaScript environments. Comparing versions 0.0.3 and 0.0.4 reveals subtle but significant differences that are essential for developers to understand. The core functionality remains consistent; both versions aim to intelligently include the necessary Babel transforms based on the target environment, eliminating the need for manual configuration of individual plugins.
A careful examination shows that the dependencies listed in both versions are exactly the same. This means that the update from 0.0.3 to 0.0.4 did not introduce any new features or bug fixes that required the addition or upgrade of underlying Babel plugins. The core set of supported transformations, handling ES2015 features, async/await, and other modern JavaScript syntax, remains identical.
For developers, this suggests the upgrade primarily addressed internal improvements or non-functional changes. It's possible that improvements to performance, build processes, or documentation were made in version 0.0.4. While no changes exists in dependencies, keeping babel-preset-env up-to-date to the latest version is usually recommended for stability, security, and potential performance enhancements, even if the list of dependencies is exactly thesame. Developers should check the change log of the patch to find out more about the changes done.
All the vulnerabilities related to the version 0.0.4 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