The babel-plugin-transform-es2015-modules-commonjs package, crucial for converting ES2015 module syntax to CommonJS format for broader compatibility, saw notable changes between versions 6.7.7 and 6.8.0. Primarily, version 6.8.0 upgraded its dependencies, pulling in newer versions of core Babel packages. Specifically, babel-types was updated to "^6.8.0" from "^6.7.7", babel-template jumped to "^6.8.0" from "^6.7.0" and babel-plugin-transform-strict-mode went to "^6.8.0" from "^6.6.5". Most significantly, babel-runtime was updated to "^6.0.0" from "^5.0.0". Developers should note that the babel-runtime upgrade is a major version bump which indicates that there might be breaking changes.
These dependency uplifts likely incorporate bug fixes, performance improvements, and new features within those respective Babel components. While the core functionality of transforming ES2015 modules remains consistent, developers upgrading should thoroughly test their builds, particularly concerning the upgrade to babel-runtime. Also, the babel-helper-plugin-test-runner devDependency was updated to "^6.8.0" from "^6.3.13". The bump in babel-helper-plugin-test-runner is important for plugin authors, offering advancements in testing infrastructure. The release dates provide a timeline context, showing approximately an eleven-day gap between versions, suggesting a focused period of development and refinement. These updates are strategically important for ensuring seamless integration and leveraging the latest advancements in the Babel ecosystem.
All the vulnerabilities related to the version 6.8.0 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