The babel-preset-stage-0 package, designed for Babel, streamlines the integration of cutting-edge JavaScript features still in the experimental "Stage 0" phase. These features are not yet standardized but are being actively explored by the JavaScript community, offering developers an early glimpse into the potential future of the language. Comparing versions 6.1.17 and 6.1.18 reveals only minor updates, primarily focused on synchronizing dependency versions. Both versions include babel-plugin-transform-do-expressions, babel-plugin-transform-function-bind, and babel-preset-stage-1 as core dependencies. The key change between these versions lies in updating these dependencies from 6.1.17 to 6.1.18. This suggests a bug fix or minor enhancement within those specific plugins or the stage 1 preset they were included in that required these minor version updates for compatibility, and stability. Developers choosing to utilize babel-preset-stage-0 gain access to these experimental features allowing them to experiment and give feedback. However, users should be aware of the unstable nature of stage-0 proposals, meaning these features may change drastically or even be dropped altogether as the JavaScript language evolves. For early adopters and those wanting to play with the newest features, this preset can be set up quickly. Developers should also be aware that this preset automatically includes babel-preset-stage-1 and its plugins. It is paramount to stay up-to-date on the status of features you are trying to use to avoid future compatibility issues and adhere to any changes in documentation for best practices
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