Babel plugin transform ES2015 modules to CommonJS version 6.14.0 introduces updates to its core dependencies compared to the previous stable version 6.11.5. Key changes lie in the updated versions of babel-types and babel-template. Version 6.14.0 depends on babel-types":"^6.14.0" and babel-template":"^6.14.0", while version 6.11.5 relies on babel-types":"^6.8.0" and babel-template":"^6.8.0". This signifies improvements and bug fixes within these underlying Babel modules, potentially affecting how the CommonJS transformation is handled.
Notably, both versions share consistent dependencies on babel-runtime and babel-plugin-transform-strict-mode, as well as the same development dependencies, ensuring a similar development and testing environment. The core functionality of transforming ES2015 module syntax (import/export) into CommonJS module syntax (require/exports) remains consistent across both versions, facilitating seamless integration into existing Node.js projects. Developers upgrading might want to explore the specific changes introduced within babel-types and babel-template between their respective versions to understand any nuanced adjustments in module transformation behavior. The consistent babel-plugin-transform-strict-mode guarantees that "use strict" directives are handled uniformly, reinforcing code safety. Consider the releaseDate, as 6.14.0 (2016-08-24) is newer than 6.11.5 (2016-07-23) and should contain more recent fixes.
All the vulnerabilities related to the version 6.14.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