The babel-plugin-transform-async-to-generator package, a crucial tool for developers using Babel, enables the transformation of modern async functions into ES2015 generator functions, ensuring compatibility with older JavaScript environments. Version 6.8.0, released on May 2nd, 2016, refines this process, building upon the foundation laid by version 6.7.4, released on March 23rd, 2016.
A key difference lies in the updated dependencies. Version 6.8.0 boasts newer versions of babel-helper-remap-async-to-generator and babel-plugin-syntax-async-functions, aligning them with the 6.8.0 release cycle. Notably, babel-runtime receives a significant update, moving from the caret-defined "^5.0.0" in 6.7.4 to "^6.0.0" in 6.8.0. This indicates potential performance enhancements, bug fixes, and new features within the runtime environment itself affecting generated code. The bump of babel-helper-plugin-test-runner to "^6.8.0" suggests improved testing infrastructure and reliability.
For developers, this means upgrading to version 6.8.0 potentially improves the async-to-generator transformation by leveraging the updated dependencies to obtain new features/fixes and an improved/more reliable compilation/testing process. While the core functionality of transforming async functions remains consistent, the underlying improvements enhance the stability and efficiency of the transpilation process. Developers should carefully consider compatibility when upgrading, particularly due to the major version bump in babel-runtime, as it could introduce breaking changes depending on the target environment.
All the vulnerabilities related to the version 6.8.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