Babel plugin transform ES2015 modules commonjs, a crucial tool for developers targeting older JavaScript environments, saw a minor update from version 6.0.15 to 6.0.18. Both versions share the same core dependencies, including babel-types, babel-runtime, babel-template, and babel-plugin-transform-strict-mode, reflecting a stable API and consistent functionality regarding ES2015 module transformation. The primary difference lies in the release date. Version 6.0.18 was published on November 3, 2015, while 6.0.15 was released on November 1, 2015.
While outwardly similar, this small jump in version number suggests internal improvements, bug fixes, or dependency updates not explicitly reflected in the listed dependencies. Developers should consider upgrading to the newer version (6.0.18) to benefit from any underlying enhancements and stability improvements, even if there is no immediate noticeable change in the core module transformation process. This plugin ensures compatibility by converting ES2015 module syntax (like import and export) into the older CommonJS format, which is understood by Node.js and older browser environments. This allows developers to write modern JavaScript code while maintaining compatibility with these environments. While the core dependencies remained consistent between these two versions, using the latest minor version is generally advisable for getting the most up-to-date and stable release of the plugin. The nature of the enhancements in the newer version are not readily available from the metadata.
All the vulnerabilities related to the version 6.0.18 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