silverstripe/framework CSV Excel Macro Injection

published 2024-05-27 2y ago modified 2024-12-02 last yr.

cvss: 8.0; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

In the CSV export feature of the CMS it's possible for the output to contain macros and scripts, which if imported without sanitisation into software (including Microsoft Excel) may be executed.

In order to safeguard against this threat all potentially executable cell values exported from CSV will be prepended with a literal tab character.

Patch / fix

fixed in 1 links 3

packagist silverstripe/framework 3.5.6, 3.6.3, 4.0.1

Is GHSA-mqjc-x563-c9q8 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 Fencer

CVSS scores

assigned by	version	score	vector
GitHub	3.1	8.0	CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
packagist	silverstripe/framework	>=3.5.0-rc1, <3.5.6 >=3.6.0-rc1, <3.6.3 >=4.0.0-rc1, <4.0.1	3.5.6 3.6.3 4.0.1

Classification

Weakness

CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component

References

Sources

GitHub Advisory GHSA-mqjc-x563-c9q8

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.