Babel-preset-env, a tool designed to simplify Babel configuration by automatically including the necessary transformations for your target environments, saw a minor update from version 0.0.8 to 0.0.9. Both versions share the same core functionality and dependencies related to ES2015 transformations and other modern JavaScript features. Developers will find they both readily handle tasks such as transforming arrow functions, classes, destructuring, and template literals, alongside async/await syntax and exponentiation operators.
The primary difference lies within the devDependencies. Version 0.0.9 uses compat-table with specific commit hash e732718eab42c6c83a364450f456474638d31f94, in comparison to the previous version 0.0.8 which uses compat-table with the #gh-pages tag. This change likely signifies a switch from tracking the gh-pages branch to pointing at a specific commit, offering more stability and predictability for testing compatibilities across browsers and JavaScript engines. While this change is primarily under-the-hood affecting development and testing, it ensures more reproducible test results during development. For developers using babel-preset-env, both versions provide a solid foundation for modern Javascript transpilation, but version 0.0.9 offers slightly increased confidence in the compatibility testing process due to the fixed compat-table. This improves the testing and development process for contributors and package maintainers.
All the vulnerabilities related to the version 0.0.9 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