GHSA-pw2q-qwvj-gh43: Cache Flooding in TYPO3 Frontend
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: typo3/cms (Packagist) 6.2.27, 7.6.11, 8.3.1.
Low priority for now. Upgrade to typo3/cms (Packagist) 6.2.27, 7.6.11, 8.3.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: OSV
Links with a valid cHash argument lead to newly generated page cache entries. Because the cHash is not bound to a specific page, attackers could use valid cHash arguments for multiple pages, leading to additional useless page cache entries. Depending on the number of pages in the system and the number of available valid links with a cHash, attackers could add a considerable amount of additional cache entries, which in the end exceed storage limits and thus could lead to the system not responding any more. This means the Cache Flooding attack potentially could lead to a successful Denial of Service (DoS) attack.
- Published
- Jun 5, 2024
- Updated
- Dec 2, 2024
- EPSS
- —
- CWE
- —
Report tools
Action score
21
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| Packagist | typo3/cms | pkg:composer/typo3/cms |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Packagist | typo3/cms | from 6.2.0 · before 6.2.27 | 6.2.27 |
| Packagist | typo3/cms | from 7.6.0 · before 7.6.11 | 7.6.11 |
| Packagist | typo3/cms | from 8.0.0 · before 8.3.1 | 8.3.1 |
Same product
Packagist: all recordsOther highest-scoring records for the same primary product.
- GHSA-67wg-6j7r-mqh8Arbitrary Code Execution in TYPO3 CMS39Monitor
- GHSA-gwfx-p7mr-f92vMissing Access Check in TYPO3 CMS36Monitor
- GHSA-8h4m-r4wm-xj7rTYPO3 Arbitrary Code Execution via File List Module35Monitor
Published before and after this one in the same product
- ← EarlierGHSA-6f9m-v7mp-7jjqJun 5, 2024 · Authentication Bypass in TYPO3 CMS0Monitor
- ← EarlierGHSA-mh3r-6cp5-hc2jJun 5, 2024 · Authentication Bypass in TYPO3 Frontend21Monitor
- Later →GHSA-c7rj-92xr-wprgJun 5, 2024 · Insecure Unserialize in TYPO3 Backend20Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Packagist:typo3/cms | 6.2.27 | Package registry (OSV) |
| Packagist:typo3/cms | 7.6.11 | Package registry (OSV) |
| Packagist:typo3/cms | 8.3.1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- Low
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
osv
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.