Babel plugin transform ES2015 modules to CommonJS, vital for projects needing to bridge modern JavaScript syntax with environments expecting the older CommonJS module system, saw a notable update with version 6.24.0 following 6.23.0. Both versions maintain the core functionality of transforming ES2015 modules and share identical dependencies for babel-types, babel-runtime, babel-template, and babel-plugin-transform-strict-mode, ensuring consistent handling of ES2015 syntax and runtime support.
The primary difference lies in the devDependencies, specifically babel-helper-plugin-test-runner. Version 6.24.0 updates this dependency to "^6.24.0" from "^6.22.0" in version 6.23.0. This suggests improvements or fixes in the test runner itself, potentially offering a more reliable or comprehensive testing environment for plugin developers. While the core functionality remains consistent, developers who write and maintain Babel plugins will find the updated test runner valuable for ensuring the stability and correctness of their code. Furthermore, the release date difference highlights the ongoing maintenance and refinement of this crucial transformation tool within the Babel ecosystem. Upgrading ensures developers benefit from the latest testing utilities, streamlining development workflows and minimizing potential integration issues.
All the vulnerabilities related to the version 6.24.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