Babel Preset Env, a powerful tool for JavaScript developers, streamlines the compilation process by intelligently determining the necessary Babel transformations based on your target environments. Versions 1.1.2 and 1.1.3 of this preset are remarkably similar, sharing identical dependencies and development dependencies, ensuring a consistent experience for users relying on core functionalities. Both versions include essential Babel plugins for transpiling modern JavaScript features like arrow functions, classes, destructuring, and modules (AMD, CommonJS, SystemJS, and UMD) to ensure compatibility across various browsers and Node.js versions.
The crucial difference lies in the releaseDate. Version 1.1.3 was released slightly later than 1.1.2 meaning that while there are no breaking changes or new functionalities it could include internal improvements, bug fixes, or dependency updates that don't affect the public API, but help to maintain or improve its reliability and performance.
For developers using Babel Preset Env, sticking to the latest stable version (1.1.3 in this case) is genearally advised to benefit from any under-the-hood enhancements and improved stability. As the dependency lists are identical in both versions there should be no worries about code compatibility while upgrading between versions. Consider this small version release as containing some bug fixes or minor internal improvements that should always be welcomed inside a modern workflow.
All the vulnerabilities related to the version 1.1.3 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