Babel preset stage-1 offers a convenient collection of Babel plugins that enable developers to utilize JavaScript features proposed for standardization but not yet finalized. This preset aligns with stage 1 of the TC39 standardization process, incorporating features considered "proposals" and undergoing active development. Versions 6.1.17 and 6.1.18 are very similar but represent iterative improvements. The key difference lies in the updated dependencies: all listed dependencies, including babel-plugin-transform-class-constructor-call, babel-plugin-transform-class-properties, babel-plugin-transform-decorators, babel-plugin-transform-export-extensions, and babel-preset-stage-2, were bumped from version 6.1.17 to 6.1.18. For developers, this means that upgrading from 6.1.17 to 6.1.18 ensures you are using the latest versions of these stage-1 related transformations with potentially bug fixes.
If you're working on a project that wants to adopt cutting-edge JavaScript syntax and features before they are officially standardized, babel-preset-stage-1 is very useful. By using this preset, you can start experimenting with new language constructs. Remember that features in stage 1 are subject to change, so compatibility with future Babel versions or standardization outcomes isn't guaranteed. It's always advised to consult the specific documentation, understand the changes introduced in each plugin, and conduct thorough testing to ensure smooth integration within your project.
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