CVE-2023-26487
Summary
| CVE | CVE-2023-26487 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2023-03-04 00:15:00 UTC |
| Updated | 2023-11-07 04:09:00 UTC |
| Description | Vega is a visualization grammar, a declarative format for creating, saving, and sharing interactive visualization designs.`lassoAppend' function accepts 3 arguments and internally invokes `push` function on the 1st argument specifying array consisting of 2nd and 3rd arguments as `push` call argument. The type of the 1st argument is supposed to be an array, but it's not enforced. This makes it possible to specify any object with a `push` function as the 1st argument, `push` function can be set to any function that can be access via `event.view` (no all such functions can be exploited due to invalid context or signature, but some can, e.g. `console.log`). The issue is that`lassoAppend` doesn't enforce proper types of its arguments. This issue opens various XSS vectors, but exact impact and severity depends on the environment (e.g. Core JS `setImmediate` polyfill basically allows `eval`-like functionality). This issue was patched in 5.23.0. |
Risk And Classification
Problem Types: CWE-79
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Vega-functions Project | Vega-functions | All | All | All | All |
| Application | Vega Project | Vega | All | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Release v5.23.0 · vega/vega · GitHub | MISC | github.com | |
| fix: lassoAppend XSS w/typecheck + array spread instead of push · vega/vega@01adb03 · GitHub | MISC | github.com | |
| XSS vulnerability in `lassoAppend` function · Advisory · vega/vega · GitHub | MISC | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.