MediumGHSA-m2hh-2m46-x6j5

silverstripe/framework may disclose database credentials during connection failure

Published 28 May 2024 · Updated 3 Dec 2024

Affected packages

silverstripe/frameworkComposer

Affected: >=3.7.0-rc1 <3.7.1
Fixed in: 3.7.1

Update to the fixed version for your release line, for example:composer require silverstripe/framework:^3.7.1

silverstripe/frameworkComposer

Affected: >=4.0.0-rc1 <4.0.5
Fixed in: 4.0.5

Update to the fixed version for your release line, for example:composer require silverstripe/framework:^4.0.5

silverstripe/frameworkComposer

Affected: >=4.1.0-rc1 <4.1.3
Fixed in: 4.1.3

Update to the fixed version for your release line, for example:composer require silverstripe/framework:^4.1.3

silverstripe/frameworkComposer

Affected: >=4.2.0-rc1 <4.2.2
Fixed in: 4.2.2

Update to the fixed version for your release line, for example:composer require silverstripe/framework:^4.2.2

Details

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.

Is GHSA-m2hh-2m46-x6j5 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected silverstripe/framework, and gives you the command that fixes it.

Scan a project free, no signup Or connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.