Babel Preset Env simplifies JavaScript development by enabling developers to utilize the latest ECMAScript features without worrying about browser compatibility. It intelligently determines the necessary Babel plugins and transformations based on your target environments, specified through browserslist or specific browser/Node.js versions. This eliminates the need for manual configuration, streamlining the build process and ensuring optimal performance.
Comparing versions 1.2.0 and 1.2.1, while the core functionality remains consistent, developers should note the release date difference. Version 1.2.1 was released on March 6, 2017, a few days after version 1.2.0 which was released on March 3, 2017. Examining the dependencies, no changes can be perceived between the versions regarding either the dependencies or the dev dependencies. Both versions include a comprehensive set of Babel plugins to handle various ES2015+ features, along with tools for testing and linting. The electron-to-chromium dependency is particularly useful for Electron developers, ensuring compatibility with the correct Chromium version. Overall, the babel-preset-env package empowers developers to write modern JavaScript while maintaining broad compatibility, making it a valuable addition to any JavaScript project. The only difference for these two versions is the release date, and no new functionalities or bugfixes exist, making both versions equal from a practical point of view.
All the vulnerabilities related to the version 1.2.1 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