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

GHSA-cwgq-83w5-8jfq silverstripe/framework

HIGHFix: silverstripe/silverstripe-framework@0610f76

GHSA-cwgq-83w5-8jfq is a high-severity (CVSS 7.5) vulnerability in silverstripe/framework. A fix is available for silverstripe/framework — see the affected versions and patch details below.

silverstripe/framework has possible denial of service attack vector when flushing

Published
May 28, 2024
Updated
Dec 3, 2024
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Dec 3, 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

A possible denial of service attack vector has been identified in the dev/build system controller.

dev/build now has its own URL token, similar to flushtoken, to ensure users are authenticated when running dev/build outside of dev environments.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistsilverstripe/framework4.0.0-rc1&&< 4.0.54.0.5composer require silverstripe/framework:^4.0.5
🐘Packagistsilverstripe/framework4.1.0-rc1&&< 4.1.34.1.3composer require silverstripe/framework:^4.1.3
🐘Packagistsilverstripe/framework4.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 4.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cwgq-83w5-8jfq 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-cwgq-83w5-8jfq can be triaged on real exposure rather than presence alone.

Tailored to GHSA-cwgq-83w5-8jfq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A possible denial of service attack vector has been identified in the dev/build system controller. dev/build now has its own URL token, similar to flushtoken, to ensure users are authenticated when running dev/build outside of dev environments.
O3 Security · Impact-Aware SCA

Is GHSA-cwgq-83w5-8jfq in your dependencies?

O3 Security finds GHSA-cwgq-83w5-8jfq across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-cwgq-83w5-8jfq: DoS (High 7.5) | O3 Security