Babel plugin transform ES2015 modules commonjs facilitates conversion of ES2015 module syntax to CommonJS format, crucial for environments lacking native ES module support, like older Node.js versions. Version 6.5.0, released on February 7, 2016, succeeds version 6.4.5, published on January 19, 2016. Examining the package information reveals minimal discernible difference in dependencies or devDependencies between the two versions. Both rely on the same versions of babel-types, babel-runtime, babel-template, babel-plugin-transform-strict-mode, and babel-helper-plugin-test-runner, suggesting the updates likely involve bug fixes, performance enhancements, or internal refactoring rather than introducing new features or modifying existing API dependencies. Developers should consider upgrading to version 6.5.0 primarily to benefit from any potential stability improvements and refinements made since the prior release. The absence of dependency shifts indicates a low-risk upgrade, unlikely to introduce compatibility issues within established projects. Always consult the corresponding changelog on the Babel GitHub repository to gain a comprehensive understanding of the specific changes implemented and determine if the fixes within that version are relevant to your specific usage scenarios for more details.
All the vulnerabilities related to the version 6.5.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