Version 6.1.20 of babel-plugin-transform-es2015-modules-commonjs is a minor update following version 6.1.18. Examining the metadata reveals the core functionality remains consistent, indicated by nearly identical dependency specifications. Both versions rely on the same versions of babel-types, babel-runtime, babel-template, babel-plugin-transform-strict-mode, and babel-helper-plugin-test-runner. This suggests the update likely involved bug fixes, performance enhancements, or internal refactoring rather than significant feature additions or API changes.
For developers using this plugin, which transforms ES2015 module syntax into CommonJS format, the upgrade from 6.1.18 to 6.1.20 should be seamless. No code modifications are expected to be necessary. The key benefit lies in potential improvements in stability or efficiency. While the specifics of these improvements are not detailed in the available metadata, the maintainers likely addressed issues identified in the previous version. Given the "patch" nature of the version bump (6.1.18 to 6.1.20), the risk of introducing breaking changes is minimal, making the update a recommended practice to leverage the latest refinements to this Babel plugin. The newer version was released on 2015-11-13, a day after the older version, this short time period reinforce the idea of an urgent bugfix or minor change.
All the vulnerabilities related to the version 6.1.20 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