Babel preset stage 2 version 6.13.0 introduces notable updates compared to the previous stable version 6.11.0, primarily focusing on expanding support for ECMAScript features further along in the standardization process. The key difference lies in the addition of two new dependencies: babel-plugin-transform-decorators and babel-plugin-transform-class-properties. This enhancement empowers developers to utilize class decorators and class properties within their JavaScript code, bringing the syntax closer to future JavaScript standards and enabling more concise and expressive class definitions.
Specifically, the inclusion of babel-plugin-transform-decorators allows developers to leverage decorators for class and method metadata, enabling patterns like dependency injection and aspect-oriented programming. babel-plugin-transform-class-properties simplifies class definitions by allowing direct declaration of properties without the need for a constructor.
For developers using Babel to transpile their code, upgrading to version 6.13.0 offers access to these powerful new features, streamlining development workflows and improving code readability. If your project already relies on decorators or class properties, or you are planning to adopt these features, updating to this version is highly recommended. However, ensure compatibility with existing code and dependencies that might be affected by these transformations. This upgrade facilitates writing modern, future-proof JavaScript code, while maintaining compatibility with older environments.
All the vulnerabilities related to the version 6.13.0 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-regenerator
No 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