Babel Preset Env, a powerful tool for modern JavaScript development, provides a Babel preset tailored to specific environments. Version 0.0.5 builds upon the foundation laid by version 0.0.4, offering developers enhanced control over their transpilation process. While both versions share core dependencies like the suite of babel-plugin-transform-es2015-* plugins for ES2015 features and browserslist for target environment definition, a subtle but significant difference emerges within the compat-table dev dependency.
In version 0.0.4, compat-table points to a specific fork (github:hzoo/compat-table#node-fix) presumably addressing node-related issues. Version 0.0.5, however, shifts to the official github:kangax/compat-table#gh-pages, suggesting a resolution of the earlier node compatibility problem and a return to the canonical source for browser compatibility data, as the tool is a table to check compatibility across browsers and javascript engines. This ensures developers are leveraging the most up-to-date and comprehensive compatibility information available.
For developers, this change signifies a move towards greater stability and reliability. By relying on the official compat-table repository, version 0.0.5 minimizes the risk of encountering issues specific to the forked version, resulting in a smoother and more predictable development experience. The core babel transformation plugins and overall functionality remain consistent, allowing developers to upgrade with confidence and continue targeting their desired environments with precision. If you have weird node related issues in your builds, consider downgrading to version 0.0.4.
All the vulnerabilities related to the version 0.0.5 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