Babel plugin transform ES2015 modules to CommonJS versions 6.18.0 and 6.16.0 offer developers a crucial tool for enabling wider compatibility in JavaScript projects by converting modern ES2015 module syntax into the widely supported CommonJS format. Version 6.18.0, released on October 24, 2016, builds upon the previous stable version 6.16.0, released on September 28, 2016, with subtle but potentially important dependency updates.
A key difference between the versions lies in their dependencies. Version 6.18.0 depends on babel-types version "^6.18.0" and babel-plugin-transform-strict-mode version "^6.18.0", while version 6.16.0 depends on babel-types version "^6.16.0" and babel-plugin-transform-strict-mode version "^6.8.0". These updates likely incorporate bug fixes, performance enhancements, or new features within those respective packages. Moreover, the devDependencies are updated with babel-helper-plugin-test-runner going from "^6.8.0" in version 6.16.0 to "^6.18.0" in the newer release, probably incorporating improvements for testing and development workflows.
Developers should consider upgrading to version 6.18.0 to benefit from the latest improvements and bug fixes within the Babel ecosystem that its updated dependencies provide. Always review the changelogs of the dependency packages babel-types, babel-plugin-transform-strict-mode and babel-helper-plugin-test-runner, to understand the specific changes included and ensure compatibility with your project. This module remains invaluable for projects targeting environments that don't natively support ES2015 modules, ensuring seamless integration and execution.
All the vulnerabilities related to the version 6.18.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