Babel Preset Env version 0.0.8 represents a minor upgrade over version 0.0.7, both designed to intelligently compile JavaScript for different environments. Examining their package metadata reveals no changes in core dependencies or development dependencies between these releases. Both versions rely on the same set of Babel plugins to transform modern JavaScript features into code compatible with older browsers and Node.js versions. This includes plugins for ES2015 features like arrow functions, classes, destructuring, and modules, as well as plugins for newer features like the exponentiation operator. Both utilize browserslist which ensures that the compilation targets only the browsers specified in the project's configuration, optimizing bundle sizes and performance by avoiding unnecessary transformations. The consistent dependency lists suggest that version 0.0.8 likely focuses on internal improvements, bug fixes, or documentation updates rather than introducing new features or modifying existing transformation behavior. For developers, this means upgrading from 0.0.7 to 0.0.8 should be a seamless and low-risk process, potentially offering improved stability or performance without requiring any code changes. While the specific changes are undocumented here, consider examining the commit history or changelog associated with version 0.0.8 to understand the precise nature of the update as it could hold improvements to configuration handling or even introduce support for newer browser versions, further streamlining the Babel compilation process.
All the vulnerabilities related to the version 0.0.8 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