Babel plugin transform ES2015 modules commonjs, versions 6.0.15 and 6.0.14, offer crucial functionality for developers seeking to convert modern JavaScript (ES2015) module syntax into the widely compatible CommonJS format. This transformation is essential for projects targeting older Node.js environments or browsers that do not natively support ES modules. Both versions share similar core dependencies including babel-types, babel-runtime, babel-template, and babel-plugin-transform-strict-mode, indicating a consistent approach to module conversion and strict mode handling.
The key difference lies in the dependency versioning and release dates. Version 6.0.15, released on November 1, 2015, depends on babel-types and babel-template version ^6.0.15 and babel-plugin-transform-strict-mode version ^6.0.15. While version 6.0.14 released only 2 days before depends on babel-types, babel-runtime, babel-template and babel-plugin-transform-strict-mode ^6.0.14.
For developers, the upgrade from 6.0.14 to 6.0.15 may include bug fixes or compatibility improvements within the Babel ecosystem. While the API remains consistent, ensuring a smooth transition, developers should always consult the official Babel changelog for detailed specifics of the included changes. The babel-runtime dependency ensures polyfills are properly managed for older environments, further solidifying the plugin's utility for broad JavaScript compatibility. Choosing the right version often depends on the specific Babel configuration and other plugins in your project to ensure compatibility.
All the vulnerabilities related to the version 6.0.15 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