Babel Preset Env streamlines JavaScript development by intelligently compiling your code for different environments. Version 1.1.1 and 1.1.0 of this npm package share a common goal: to let developers use the latest JavaScript features without worrying about browser compatibility. Both versions automatically include the necessary Babel plugins to transform modern code into a format that older browsers and environments can understand. This eliminates the need for developers to manually manage individual Babel plugins, saving time and effort.
The core functionality remains consistent across both versions, with identical dependencies on crucial Babel plugins like transform-es2015-* for ES6 features and transform-async-to-generator for asynchronous functions. This ensures that developers can leverage features like arrow functions, classes, and async/await syntax with confidence. The browserslist dependency in both versions empower babel-preset-env to target specific browsers and versions, optimizing the output for the desired environment.
However, a subtle difference exists in the repository URL within the package metadata. While both versions point to the same GitHub repository, version 1.1.0 uses the git+https protocol. While this difference doesn't affect the functionality, small optimization such as this could be included. Version 1.1.1 was released just minutes after the previous one and potentially contains very small improvements and under the hood changes.
All the vulnerabilities related to the version 1.1.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