Babel plugin transform ES2015 modules to CommonJS, versions 6.24.1 and 6.24.0 offer developers a crucial tool for converting modern JavaScript module syntax into the widely supported CommonJS format, ensuring compatibility across diverse environments. Version 6.24.1, released on April 7, 2017, builds upon the earlier 6.24.0 version from March 13, 2017, primarily through dependency updates. Notably, 6.24.1 upgrades babel-types and babel-template to version 6.24.1 and babel-plugin-transform-strict-mode to version 6.24.1. Version 6.24.0 uses "babel-types":"^6.23.0","babel-template":"^6.23.0","babel-plugin-transform-strict-mode":"^6.22.0". While the core functionality remains consistent between the two, developers should prioritize the latest version, 6.24.1, to benefit from the newest features and bug fixes incorporated within its updated dependencies. Both versions share the same core purpose: enabling developers to seamlessly transition ES2015 module syntax (like import and export) into the CommonJS format (using require and module.exports), streamlining module handling and ensuring broader compatibility, specifically in Node.js environments. The babel-runtime dependency remain on version 6.22.0 on both versions. With a permissive MIT license, and available through npm, the packages are easy to incorporate into development workflows.
All the vulnerabilities related to the version 6.24.1 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