Babel Preset Env 1.3.0 introduces subtle but noteworthy changes compared to its predecessor, version 1.2.2. Primarily, the update focuses on refinements within the development dependencies, aiming for enhanced tooling and testing capabilities. The key difference lies in the updated electron-to-chromium dependency, moving from version 1.2.6 to 1.3.2. This update reflects the ongoing effort to maintain compatibility with the latest Electron releases, ensuring seamless integration for developers targeting that platform.
For developers using Babel Preset Env, this increment signifies an improvement in the underlying infrastructure. Although the core functionality remains consistent, the updated electron-to-chromium dependency contributes to better accuracy in identifying the required Babel transformations for code targeting specific Electron versions. This indirectly translates to more reliable and optimized transpilation, particularly crucial for Electron-based applications.
While not a groundbreaking release, version 1.3.0 demonstrates a commitment to continuous improvement and staying current with the evolving JavaScript ecosystem. By keeping its development dependencies up-to-date, Babel Preset Env ensures a more robust and dependable experience for its users, especially those working with modern web technologies and application frameworks. The update streamlines the development workflow related to Electron applications, offering more precise targeting and transpilation.
All the vulnerabilities related to the version 1.3.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-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