silverstripe/framework may disclose database credentials during connection failure

published 2024-05-28 2y ago modified 2024-12-03 last yr.

cvss: 6.5; 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

When running SilverStripe 3.7 or 4.x in dev mode with the mysqli database driver, there is a potential to disclose the connection details.

We have blacklisted the sensitive parts of the connection information from being included in dev mode stack traces when database errors occur.

Patch / fix

fixed in 1 links 3

packagist silverstripe/framework 3.7.1, 4.0.5, 4.1.3, 4.2.2

Is GHSA-m2hh-2m46-x6j5 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	6.5	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
packagist	silverstripe/framework	>=3.7.0-rc1, <3.7.1 >=4.0.0-rc1, <4.0.5 >=4.1.0-rc1, <4.1.3 >=4.2.0-rc1, <4.2.2	3.7.1 4.0.5 4.1.3 4.2.2

Classification

Weakness

CWE-209 Generation of Error Message Containing Sensitive Information

References

Sources

GitHub Advisory GHSA-m2hh-2m46-x6j5

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.