Babel plugin transform ES2015 modules to CommonJS, a crucial tool for developers targeting environments that don't natively support ES modules. Version 6.23.0, released on February 14, 2017, builds upon the solid foundation of version 6.22.0, released on January 20, 2017, providing incremental improvements and dependency updates. Key dependencies like babel-types, babel-runtime, babel-template, and babel-plugin-transform-strict-mode saw corresponding version bumps to ^6.23.0 where applicable, ensuring compatibility and access to the latest features and bug fixes within those core Babel components. While the core functionality of transforming ES2015 modules to CommonJS remains consistent between the two versions, developers upgrading to 6.23.0 benefit from these dependency updates, which often include performance enhancements, bug resolutions, and alignment with the evolving Babel ecosystem. Both versions share the same MIT license and are maintained within the Babel repository on GitHub, illustrating a commitment to open-source principles and community collaboration. Developers should always consider upgrading to the latest available version to leverage the most up-to-date features, stability improvements, and security patches within the Babel toolchain; therefore, 6.23.0 is the recommended version.
All the vulnerabilities related to the version 6.23.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