Babel Preset Env is a powerful tool for JavaScript developers, allowing them to use the latest JavaScript features while ensuring compatibility with a wide range of browsers and environments. Version 1.1.10 is a minor update following the previous stable version 1.1.9, both designed to intelligently compile JavaScript code based on the target environment specified.
Examining the dependencies and devDependencies reveals that the core functionality and underlying tools remain consistent between the two versions. Both rely on the same suite of Babel plugins for transforming ES2015+ syntax, alongside essential utilities like browserslist for determining browser support and electron-to-chromium for Electron compatibility. Development dependencies related to testing, linting, and code formatting are also identical, pointing to a stable and well-maintained codebase. No changes in dependencies.
The key difference is the releaseDate. Version 1.1.10 was released on 2017-02-24 at 20:48:42.994Z, whereas version 1.1.9 was released earlier on the same day at 13:35:19.444Z. While the precise nature of the updates within those few hours isn’t explicitly detailed in the package data, it is likely to includes bug fixes, performance improvements, or minor adjustments to the browser compatibility logic.
All the vulnerabilities related to the version 1.1.10 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