Babel plugin transform ES2015 modules commonjs, versions 6.6.5 and 6.6.4, serve the purpose of transforming ES2015 modules into the commonjs module format. This is crucial for developers targeting Node.js environments or older browsers that don't natively support ES2015 module syntax. Both versions share the same core functionality and dependencies: Babel types, Babel runtime, Babel template, and Babel plugin transform strict mode, ensuring compatibility with the Babel ecosystem. The MIT license grants developers the freedom to use and modify the plugin. The primary difference lies within the minor version bump which suggests bug fixes and very small improvements between the 6.6.4 and 6.6.5 releases.
Developers incorporating this plugin into their Babel configuration can expect a seamless transformation process. The "babel-helper-plugin-test-runner" in devDependencies, assures robust testing capabilities. While the core dependencies remain consistent, developers should always ensure they're using compatible versions of the Babel ecosystem components. Specifically, when upgrading from 6.6.4 to 6.6.5, verify that your existing Babel configuration and dependent plugins are fully compatible. The "releaseDate" indicates a small gap in time, suggesting that fixes or minor enhancements prompted the update. Though incremental, these updates contribute to the stability and reliability of the plugin within a Babel-driven build pipeline. Keep an eye on official Babel release notes, as they often detail the specific fixes or enhancements included in minor version bumps like this one.
All the vulnerabilities related to the version 6.6.5 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