Babel plugin transform ES2015 modules to CommonJS, streamlining modern JavaScript code for compatibility with older environments. Version 6.0.14 builds upon the foundation laid by version 6.0.12, offering crucial refinements and dependency updates of babel-types, babel-runtime and babel-template to versions ^6.0.14 for enhanced stability and performance within the Babel ecosystem. Note that version 6.0.12 has babel-plugin-transform-strict-mode version set to ^6.0.2, while version 6.0.14 has the version set to ^6.0.14.
Both versions share the same core functionality: transforming ES2015 module syntax (import/export) into the CommonJS format (require/module.exports), which is commonly used in Node.js. This ensures your modern JavaScript code works seamlessly in environments that haven't fully adopted ES modules. Using this plugin allows developers who use Babel to standardize their module handling across their codebase and compile target environments.
Developers should upgrade to 6.0.14 to benefit from the dependency updates, ensuring code relies on the latest patches and features available in supporting Babel packages. If you're already using 6.0.12 and haven't encountered any issues related to those dependencies, the upgrade remains a worthwhile consideration for staying up-to-date; however, review any potential breaking changes introduced by the updated Babel packages.
All the vulnerabilities related to the version 6.0.14 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