Babel plugin transform ES2015 modules to CommonJS, versions 6.4.5 and 6.4.0, offer a crucial transformation for developers targeting Node.js or browsers utilizing CommonJS module systems. This Babel plugin enables the use of modern ES2015 module syntax, like import and export, while ensuring compatibility with environments that haven't fully adopted these newer standards. Both versions share the same core functionality, installation instructions and license (MIT). They rely on babel-types, babel-runtime, babel-template and babel-plugin-transform-strict-mode as dependencies and babel-helper-plugin-test-runner for development.
The key difference lies in the dependency babel-types. Version 6.4.5 depends on babel-types version "^6.4.5", while version 6.4.0 depends on babel-types version "^6.4.0". This difference, although small, highlights that version 6.4.5 includes updates or bug fixes related to the babel-types package. Developers upgrading from 6.4.0 to 6.4.5 should review the changelog for babel-types version 6.4.5 for the exact changes and potential impact on their project. Version 6.4.5 was released on January 19, 2016, about two weeks after version 6.4.0 which released on January 6, 2016. If you are choosing which version to install, it's advisable to use version 6.4.5. as it's the latest one and includes the latest changes.
All the vulnerabilities related to the version 6.4.5 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