Babel Preset React App streamlines the integration of essential Babel transformations for React projects, particularly geared towards those leveraging Create React App. Version 2.0.1, released on December 7th, 2016, builds upon the foundation of its predecessor, version 2.0.0, which was released a few days prior, on December 3rd, 2016.
Upon inspection, the most significant difference for developers is the addition of babel-plugin-transform-es2015-parameters as a dependency. While the majority of the dependency versions remain consistent between the two releases including core components like babel-runtime, babel-preset-react, and various babel-plugin-transform-* modules, the inclusion of the ES2015 parameter transformation plugin in version 2.0.1 provides improved support for default function parameters and rest parameters, making code cleaner and more concise. This new addition empowers developers to utilize modern JavaScript parameter features within their React components, enhancing code readability and reducing boilerplate.
For developers already using version 2.0.0, upgrading to version 2.0.1 grants access to this enhanced ES2015 parameter support without necessitating any fundamental code changes. This is a minor version bump ensuring backward compatibility and ease of adoption for existing React projects. Both versions prioritize providing a robust Babel configuration tailored for modern React development. They offer a set of curated plugins optimized for React's JSX syntax and modern JavaScript features, ultimately simplifying the build process for React applications.
All the vulnerabilities related to the version 2.0.1 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