Babel plugin transform ES2015 modules to CommonJS, converting modern JavaScript module syntax (ES modules) into the older CommonJS format. This translation ensures compatibility with environments that don't natively support ES modules, like older Node.js versions or some bundlers. The versions 6.11.5 and 6.10.3 share identical dependency requirements including core Babel tools like babel-types, babel-runtime, babel-template, and babel-plugin-transform-strict-mode ensuring that both versions function within a similar ecosystem and that ensures API backward compatibility for most users. They also employ the same testing framework (babel-helper-plugin-test-runner) during the development process.
The key distinction between these releases lies in their release dates. Version 6.11.5 was published on July 23, 2016, approximately a month after version 6.10.3 released on June 18, 2016. While the specific changes incorporated within version 6.11.5 aren't explicitly detailed here, the release date suggests that it incorporates bug fixes, performance enhancements, or minor feature refinements implemented since the previous stable release. Users are encouraged to update to the newer version to benefit from these improvements and maintain compatibility with the latest tooling. Both versions are MIT licensed and available on GitHub underlining the community support.
All the vulnerabilities related to the version 6.11.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