Babel plugin transform async to generator version 6.7.0 and 6.5.0 are designed to convert async functions into ES2015 generators, enabling compatibility with older JavaScript environments. Both versions share the core functionality of transforming async/await syntax, a valuable tool for developers targeting various platforms. Key dependencies like babel-plugin-syntax-async-functions and babel-runtime remain consistent, ensuring the parsing of async functions and providing necessary runtime support.
The primary difference lies in the updated dependency on babel-helper-remap-async-to-generator. Version 6.7.0 uses "^6.7.0" while version 6.5.0 depends on "^6.4.6". This helper module likely contains refinements and bug fixes related to the core transformation logic. Developers upgrading to 6.7.0 can expect improved accuracy and stability in the async-to-generator conversion process. While both versions utilize babel-helper-plugin-test-runner for robust testing, the slight difference in the babel-helper-remap-async-to-generator dependency suggests incremental improvements. Developers should consider upgrading to version 6.7.0 for the latest enhancements in async/await transformation, potentially mitigating subtle issues and ensuring better adherence to the ES2015 generator pattern. Both versions are MIT licensed and found in the babel repository.
All the vulnerabilities related to the version 6.7.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