Babel plugin transform ES2015 modules commonjs, a crucial tool for developers using Babel to transpile modern JavaScript (ES2015+) into the widely compatible CommonJS module format, saw an update from version 6.5.2 to 6.6.0. This update, released on February 29, 2016, builds upon the functionality of the previous version, released on February 12, 2016, ensuring smoother integration with existing CommonJS environments.
A key difference lies in the updated dependencies. Babel-types jumped from version 6.5.2 to version 6.6.0 and babel-template moved from 6.3.13 to 6.6.0. While babel-runtime and babel-plugin-transform-strict-mode remained untouched, indicating a stability in these core aspects of the transformation process. The update likely addressed bug fixes, performance enhancements, and potentially incorporated new features related to handling ES2015 modules within a CommonJS context. Developers relying on the plugin should note the change in the version numbers of babel-types and babel-template, to ensure compatibility within their broader toolchain. Those using older tools might experience errors if the version ranges are tightly controlled. The update promotes more robust and accurate transpilation of ES2015 module syntax like import and export into the require and module.exports patterns familiar to CommonJS environments, making it easier to integrate modern JavaScript code into Node.js projects and other CommonJS-based systems.
All the vulnerabilities related to the version 6.6.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