Babel-traverse 6.26.0 represents a notable update over its predecessor, version 6.25.0, offering developers refinements and dependency upgrades crucial for modern JavaScript transformation. The core functionality, described as maintaining the overall tree state and handling node replacement, removal, and addition, remains consistent. However, under the hood, several dependencies have been bumped to newer versions.
Specifically, key dependencies such as babel-code-frame, babel-runtime, and babel-types have been updated to ^6.26.0, aligning them with the core package version and potentially introducing bug fixes, performance improvements, or new features within those modules. Babylon also sees an upgrade from 6.17.2 to 6.18.0, incorporating the latest syntax parsing capabilities. Furthermore, notable updates appear in debug (from 2.2.0 to ^2.6.8), globals (from ^9.0.0 to ^9.18.0), and lodash (from ^4.2.0 to ^4.17.4), providing developers with the benefits of enhanced debugging tools, comprehensive global variable support, and optimized utility functions. Even babel-generator, a dev dependency, gets bumped to ^6.26.0.
These dependency updates collectively contribute to a more robust and feature-rich experience for developers using babel-traverse. By staying current with its dependencies, version 6.26.0 ensures greater compatibility with the evolving JavaScript landscape and allows developers to leverage the latest advancements in the Babel ecosystem. The release date of August 16, 2017, provides historical context for developers assessing the relevance and maturity of this version within their projects.
All the vulnerabilities related to the version 6.26.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