Babel Preset Env, a powerful tool for modern JavaScript development, simplifies the process of configuring Babel by intelligently determining the necessary transformations based on your target environments. Versions 1.6.1 and 1.6.0 offer developers a streamlined way to write cutting-edge JavaScript without worrying about browser compatibility.
Examining the changes between version 1.6.0 and 1.6.1, the core functionality remains consistent, with both providing comprehensive ES2015+ support through a suite of Babel plugins. Key dependencies like babel-plugin-check-es2015-constants and various transform plugins remain at the same versions ensuring stability in core ES2015 transformations. Both versions use browserslist to target specific browsers and semver for version management.
The significant difference lies within the devDependencies. In version 1.6.0, compat-table is from commit d88c80ea6dcbc7064112eb46bb020718107892f7 on github while in version 1.6.1 it's from commit 957f1ff15972e8fb2892a172f985e9af27bf1c75. This suggests an update to the compatibility data used for testing and might reflect newer browser support information or bug fixes within the tests. This difference is primarily important for maintainers and contributors focused on comprehensive browser compatibility testing rather than end-users integrating Babel Preset Env into their projects. Developers using either version can expect robust ES2015+ transformation tailored to specified browser environments.
All the vulnerabilities related to the version 1.6.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