The babel-plugin-transform-es2015-modules-commonjs package, essential for converting ES2015 modules into CommonJS format for broader compatibility, saw a version update from 6.8.0 to 6.10.3. Both versions share the same core dependencies including babel-types, babel-runtime, babel-template, and babel-plugin-transform-strict-mode, all at compatible versions ensuring a degree of consistency in functionality. Similarly, the devDependencies also remain consistent.
Delving deeper the key distinction lies primarily in the release date, moving from May 2nd, 2016 for 6.8.0, to June 18th, 2016 for version 6.10.3. This signifies a period where bug fixes, performance improvements or minor feature adjustments was implemented. Developers should typically prefer the newer version (6.10.3) as it likely incorporates the latest refinements and stability enhancements at the time.
The consistency in dependencies suggests no breaking API changes occur between these versions, facilitating a smooth upgrade. If you are currently using babel to transform es2015 modules into commonjs, upgrading ensures you benefit from an iteration of software fixes and improvements. Check the changelog associated with babel to identify what specifically the 6.10.3 addresses.
All the vulnerabilities related to the version 6.10.3 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