NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

silverstripe/framework may disclose database credentials during connection failureGHSA-m2hh-2m46-x6j5

MEDIUMFix: silverstripe/silverstripe-framework@214e281

GHSA-m2hh-2m46-x6j5 is a medium-severity (CVSS 6.5) vulnerability in silverstripe/framework. A fix is available for silverstripe/framework — see the affected versions and patch details below.

Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Dec 3, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

4 pkgs affected
🐘silverstripe/framework🐘silverstripe/framework🐘silverstripe/framework🐘silverstripe/framework

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistsilverstripe/framework≥ 3.7.0-rc1&&< 3.7.13.7.1composer require silverstripe/framework:^3.7.1
🐘Packagistsilverstripe/framework≥ 4.0.0-rc1&&< 4.0.54.0.5composer require silverstripe/framework:^4.0.5
🐘Packagistsilverstripe/framework≥ 4.1.0-rc1&&< 4.1.34.1.3composer require silverstripe/framework:^4.1.3
🐘Packagistsilverstripe/framework≥ 4.2.0-rc1&&< 4.2.24.2.2composer require silverstripe/framework:^4.2.2

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for silverstripe/framework, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update silverstripe/framework to 3.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m2hh-2m46-x6j5 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-m2hh-2m46-x6j5 in your dependencies?

Find it across Packagist, including transitive dependencies.

GHSA-m2hh-2m46-x6j5: framework — Fixed in 3.7.1