Babel plugin transform ES2015 modules to CommonJS, version 6.2.0, introduces key updates focusing on strengthened internal dependencies, contrasting with its predecessor, version 6.1.20. A primary difference lies in the updated dependencies; version 6.2.0 upgrades babel-types and babel-template to version ^6.2.0, and babel-plugin-transform-strict-mode to ^6.2.0, while the prior stable version, 6.1.20, relies on babel-types, babel-template, and babel-plugin-transform-strict-mode at version ^6.1.18. Developers need to note this shift, as it may influence compatibility with other Babel plugins or core functionalities within their projects.
The dependency on babel-runtime remains consistent across both versions at ^5.0.0, and the developer tooling dependency, babel-helper-plugin-test-runner, also stays put at ^6.1.18. These similarities ensure a degree of continuity in the development workflow.
The update essentially brings core Babel tools in line with the newer iterations, which likely incorporate bug fixes, performance enhancements, or new features within those core modules. Developers upgrading should test their builds thoroughly to ensure seamless integration with the updated dependencies. The targeted use case largely remains the same: enabling the compilation of ES2015 module syntax into CommonJS, optimizing code for wider compatibility with diverse JavaScript environments, especially Node.js. The MIT license ensures open usage and modification, inviting developers to adapt and innovate using this plugin.
All the vulnerabilities related to the version 6.2.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