Babel plugin transform async to generator, a crucial tool for developers targeting ES2015 environments while utilizing modern async/await syntax, saw a subtle but notable update between versions 6.1.17 and 6.1.18. Both versions serve the core purpose of transforming asynchronous functions into ES2015 generator functions, ensuring compatibility across older JavaScript runtimes. Key dependencies like babel-helper-remap-async-to-generator, babel-plugin-syntax-async-functions, and babel-runtime remain consistent in enabling this transformation.
The upgrade introduces updated versions of the dependency packages babel-helper-remap-async-to-generator and babel-plugin-syntax-async-functions from 6.1.17 to 6.1.18. While specifics of minor changes are not listed, this indicates refinement in handling async/await syntax or improvements in the code generation process. Developers benefit from the upgrade through possible bug fixes, improved performance in async function transformation, and better alignment with the latest ECMAScript standards.
Furthermore, the updated version includes babel-helper-plugin-test-runner at version 6.1.18 enhancing the reliability and robustness of babel plugin. Released moments apart on November 12, 2015, these versions demonstrate ongoing maintenance and attention to detail, reinforcing the plugin's stability for production use. Those employing the Babel plugin will find updating advantageous, ensuring they're leveraging the most refined and reliable implementation of async/await transformation for their projects.
All the vulnerabilities related to the version 6.1.18 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