CVE-2023-26487 json
Vega has cross-site scripting vulnerability in `lassoAppend` function
published 3y ago modified 2mo ago also EUVD-2023-1128 , GHSA-w5m3-xh75-mp55
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 57%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm vega 5.23.0
- npm vega-functions 5.13.1
- vega-functions_project vega-functions 5.13.1
- vega_project vega 5.23.0
- vega.js Debian 14, Debian 13 5.25.0+ds+~cs5.3.0-1
debian advisories DEBIAN-CVE-2023-26487
Is CVE-2023-26487 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2023-26487 updated cvss 6.1
kibana: xss in custom visualizations
-
Red Hat JBoss Fuse 6 kibana kibana Red Hat JBoss Fuse Service Works 6 kibana kibana Red Hat OpenShift Container Platform 3.11 kibana, kibana kibana, openshift3/ose-logging-kibana5affected: no fix planned “Out of support scope”
-
Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/kibana6-rhel8, openshift-logging/cluster-logging-rhel8-operatornot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.81% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-15).
Exploits and checks
- github.com https://github.com/vega/vega/security/advisories/GHSA-w5m3-xh75-mp55 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
| GitHub | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | vega | <5.23.0 |
5.23.0 |
| npm | vega-functions | <5.13.1 |
5.13.1 |
Affected products
- vega vega
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/vega/vega/commit/01adb034f24727d3bb321bbbb6696a7f4cd91689
web, patch
-
github.com
/vega/vega/security/advisories/GHSA-w5m3-xh75-mp55
web, exploit, third-party-advisory, advisory
-
github.com
/vega/vega/releases/tag/v5.23.0
web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2023-26487
advisory
-
github.com
/vega/vega
package
Sources
- CVE List CVE-2023-26487
- GitHub Advisory GHSA-w5m3-xh75-mp55
- NVD CVE-2023-26487
- Maintainer advisory GHSA-w5m3-xh75-mp55
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of vega/vega published their own advisory on GitHub. Reviewed sources take precedence over it.