Babel Preset Env, a powerful tool for modern JavaScript developers, simplifies Babel configuration by enabling the use of the latest ECMAScript features without manually managing individual plugins. This preset intelligently determines the necessary transformations based on the target environment, whether it's a specific browser or Node.js version.
Comparing versions 1.1.3 and 1.1.4 reveals subtle differences, primarily in the release date, with version 1.1.4 being released momentarily after 1.1.3. While the core dependencies and development dependencies remain identical, including essential Babel plugins for ES2015 transformations, async/await support, and various syntax features, the updated version suggests a potential for minor bug fixes or very small enhancements under the hood.
For developers, Babel Preset Env offers significant advantages. It streamlines the development workflow by eliminating plugin management and ensuring compatibility across environments. Key dependencies like browserslist allow fine-grained control over targeted browsers. Development dependencies such as eslint with associated plugins ensure code quality and consistency. The consistent dependency list between the two versions highlight the stability and reliability of this very useful preset. Upgrading from 1.1.3 to 1.1.4 is very likely to be seamless and with almost no effort.
All the vulnerabilities related to the version 1.1.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