The babel-plugin-transform-es2015-modules-commonjs package, crucial for transforming ES2015 modules into CommonJS format for broader compatibility, saw a minor version update from 6.1.4 to 6.1.5. Released just a day apart, these versions offer valuable insights for developers managing Babel transformations.
Version 6.1.5 brings updated dependencies, notably on babel-types and babel-template, bumping them up to version 6.1.5 from 6.1.4 and 6.0.15 respectively. The babel-plugin-transform-strict-mode and babel-helper-plugin-test-runner dependencies are update as well. These dependency upgrades likely incorporate bug fixes, performance improvements, or new features within those core Babel modules. While seemingly small, these changes can significantly impact the overall stability and efficiency of the transformation process.
For developers, this means upgrading to 6.1.5 could resolve potential issues encountered with older versions of babel-types or babel-template. Developers using babel-plugin-transform-es2015-modules-commonjs should evaluate these dependency updates to ensure compatibility with their existing Babel configuration and project dependencies. This update ensures you're leveraging the latest refinements in Babel's ecosystem, leading to more robust and optimized code transformations from ES2015 modules to CommonJS.
All the vulnerabilities related to the version 6.1.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