The npm package babel-preset-stage-2 version 6.0.14 provides a configuration for Babel, the JavaScript transpiler, enabling support for ECMAScript features currently at Stage 2 of the TC39 standardization process. This version bundles together several Babel plugins and a preset, streamlining the process of using these features in your JavaScript code. Key dependencies include babel-preset-stage-3, ensuring compatibility with features further along in the standardization pipeline, and babel-plugin-transform-object-rest-spread, which allows developers to utilize the object rest and spread syntax for cleaner object manipulation. Crucially, it also incorporates babel-plugin-syntax-trailing-function-commas, enabling trailing commas in function parameters, improving code readability and reducing potential errors. This preset simplifies development by enabling modern JavaScript syntax while maintaining broad browser compatibility through transpilation. It's a valuable tool for developers eager to use bleeding-edge features without sacrificing compatibility. Released in October 2015, this specific version offers a snapshot of JavaScript evolution at that time. Compared to the previous *undefined* version, this version incorporates specific fixes, potentially addressing bugs and improving performance and features. Developers should carefully consider the specific changes in these dependencies when upgrading to ensure that their code remains compatible and benefits from the improvements.
All the vulnerabilities related to the version 6.0.14 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