Babel preset stage 1 facilitates the use of JavaScript features currently under consideration for standardization, offering developers an early glimpse and testing ground for potential future language enhancements. Comparing versions 6.2.4 and 6.3.13 of this preset reveals key updates in its dependency inclusions, crucial for those employing cutting-edge JavaScript functionalities.
The most significant change lies in the updated versions of its core dependencies. Both versions include 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 for inheritance. Version 6.2.4 relies on version 6.2.4 of all those dependencies, while version 6.3.13 uses version 6.3.13. These updates likely incorporate bug fixes, performance improvements, and possibly new features within each respective transformation, enhancing the reliability and efficiency of the code transpiled using the preset.
Developers upgrading from 6.2.4 to 6.3.13 should review the changelogs for each updated dependency to understand the specific changes introduced. This ensures compatibility with existing code and allows them to leverage any new capabilities offered by the updated transformations. Using babel-preset-stage-1 allows developers to experiment with features like class properties and decorators, offering a forward-thinking approach to JavaScript development. However, it's crucial to remember that stage 1 features are subject to change or removal from the language specification, so using them in production environments should be carefully considered.
All the vulnerabilities related to the version 6.3.13 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