Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Informational severity, published 2 March 2023.
- Which products and versions are affected?
- vega (npm) SEMVER:introduced=5.0.0,fixed=5.4.1.
- Is there a fix for This vulnerability?
- Yes. vega (npm): upgrade to 5.4.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network.
- Am I affected?
- Check whether you run vega (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- vega (npm): upgrade to 5.4.1 or later
npm install vega@5.4.1
Technical details
The vulnerability is an arbitrary code execution flaw triggered when clicking href links in Vega visualizations. The root cause involves improper handling or validation of href attributes, allowing injection of executable code. The attack vector is user interaction—a victim must click a malicious href link embedded in a Vega visualization. No authentication is required, but the attacker must craft a malicious Vega specification or modify an existing one. Successful exploitation allows arbitrary code execution in the user's browser context. Patches were released in versions 5.4.1 and 4.5.1.
Affected products
- Vega Vega all versions before 4.5.1; 5.0.0 through 5.4.0
Timeline
- 2023-03-02: disclosed