Babel Preset Env simplifies JavaScript compilation by automatically including the necessary Babel plugins based on your target environments. Comparing versions 1.5.0 and 1.4.0, developers will notice key updates in dependency management. In the newer 1.5.0, peer dependency issues are resolved. Browserslist, a crucial tool for specifying target browsers, sees an update from version ^1.4.0 to ^2.1.2. This enhancement empowers developers with more precise control over browser compatibility, ensuring their code runs seamlessly across varied platforms. Several other dependencies have seen minor version bumps.
Furthermore, the compat-table dev dependency is updated from commit 861954b6e13d3eaa1ba9ef1a016906c0fc1072db to 1f0bb0913736fe8c4c11b139766c73b9cbedb9f2. Most notably, babel-preset-es2015 and babel-plugin-transform-flow-strip-types which were dependencies in version 1.4.0, are removed in version 1.5.0. These changes reflect Babel's ongoing efforts to streamline the preset, reduce redundancy, and improve the developer experience. By leveraging Babel Preset Env, developers can confidently write modern JavaScript without worrying about manual plugin configuration, saving time and effort while ensuring optimal browser support. This makes it a valuable tool for modern web development workflows.
All the vulnerabilities related to the version 1.5.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