Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
CRITICAL severity

GHSA-8v6m-7f5v-hhx6 silverstripe/framework

CRITICALFix: silverstripe/silverstripe-framework@f32c893

GHSA-8v6m-7f5v-hhx6 is a critical-severity (CVSS 9.1) vulnerability in silverstripe/framework. A fix is available for silverstripe/framework — see the affected versions and patch details below.

Silverstripe Brute force bypass on default admin

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

Real-World Exposure

3 pkgs affected
🐘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

Default Administrator accounts were not subject to the same brute force protection afforded to other Member accounts. Failed login counts were not logged for default admins resulting in unlimited attempts on the default admin username and password.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistsilverstripe/framework3.1.18&&< 3.1.193.1.19composer require silverstripe/framework:^3.1.19
🐘Packagistsilverstripe/framework3.2.3&&< 3.2.43.2.4composer require silverstripe/framework:^3.2.4
🐘Packagistsilverstripe/framework3.3.1&&< 3.3.23.3.2composer require silverstripe/framework:^3.3.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.1.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8v6m-7f5v-hhx6 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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-8v6m-7f5v-hhx6 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-8v6m-7f5v-hhx6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Default Administrator accounts were not subject to the same brute force protection afforded to other Member accounts. Failed login counts were not logged for default admins resulting in unlimited attempts on the default admin username and password.
O3 Security · Impact-Aware SCA

Is GHSA-8v6m-7f5v-hhx6 in your dependencies?

O3 Security finds GHSA-8v6m-7f5v-hhx6 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-8v6m-7f5v-hhx6: silverstripe/framework | O3 Security