Highcharts DataTable prototype pollution in single-cell writes
highcharts · @highcharts dashboards · @highcharts grid-pro
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @highcharts/dashboards npm |
|
|
| @highcharts/grid-pro npm |
|
|
highcharts · @highcharts dashboards · @highcharts grid-pro
| Product | Affected | Fixed in |
|---|---|---|
| @highcharts/dashboards npm |
|
|
| @highcharts/grid-pro npm |
|
|
Highcharts JS is a JavaScript charting library based on SVG. From 1.0.0 until Dashboards 4.2.2, and from 2.0.0 until Grid Pro 3.2.0, Highcharts DataTable single-cell writers use an untrusted column ID as a key without rejecting __proto__ or constructor. DataTable.setCell, including Dashboards connector write-back and Grid Pro editing paths, can therefore write integer-indexed values onto Object.prototype or the Object constructor. In Dashboards releases with column aliases, a literal __proto__ ID is redirected by the alias map, while an alias targeting __proto__ reaches the unsafe write; later releases without aliases accept the unsafe ID directly. Those inherited values affect array and object reads and for-in enumeration throughout the page, which can alter application control flow or disrupt rendering. Exploitation requires control of the table or component column ID and a cell, point, or API write. This issue is fixed in Dashboards 4.2.2 and Grid Pro 3.2.0.
From the CVE record · GitHub_M
Highcharts DataTable single-cell writers do not reject unsafe column IDs, allowing writes to Object.prototype or the Object constructor. An attacker who controls a table or component column ID and a cell, point, or API write can affect reads and enumeration across the page, potentially altering application control flow or disrupting rendering.
Teams using npm @highcharts/dashboards versions >=1.0.0 <4.2.2 or @highcharts/grid-pro versions >=2.0.0 <3.2.0 should check their deployments.