Babel preset stage 1 offers developers a convenient way to incorporate cutting-edge JavaScript features into their projects that are under consideration for standardization. Comparing version 6.2.4 with the older 6.1.18, the key difference lies primarily in the synchronized versioning of its dependencies. Both versions bundle essential Babel plugins required to transform JavaScript code adhering to stage 1 proposals like transform-class-constructor-call, transform-class-properties, transform-decorators, and transform-export-extensions. Additionally, they depend on babel-preset-stage-2, creating a chain of presets for progressive adoption of newer Javascript features.
The upgrade from 6.1.18 to 6.2.4 ensures that all these plugins and the stage-2 preset are aligned at version 6.2.4. This is essential for preventing potential compatibility issues and ensuring a consistent compilation process. For developers, upgrading to 6.2.4 is a straightforward path to benefit from improvements and bug fixes present in the aligned dependency versions. While functionality is very similar, updating to the newest version ensures you are working with the latest bug fixes.
All the vulnerabilities related to the version 6.2.4 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