CVE-2024-34358: TYPO3 vulnerable to an Uncontrolled Resource Consumption in the ShowImageController
Problem The ShowImageController (eID txcmsshowpic) lacks a cryptographic HMAC-signature on the frame HTTP query parameter (e.g. /index.php?eID=txcmsshowpic?file=3&...&frame=12345). This allows adversaries to instruct the system to produce an arbitrary number of thumbnail images on the server side.
Published May 14, 2024
Affected packages
typo3/cms-core
- Ecosystem
- Composer (PHP)
- Affected
- >= 9.0.0, <= 9.5.47
- Fixed in
- 9.5.48
- Check
composer show typo3/cms-core
typo3/cms-core
- Ecosystem
- Composer (PHP)
- Affected
- >= 10.0.0, <= 10.4.44
- Fixed in
- 10.4.45
- Check
composer show typo3/cms-core
typo3/cms-core
- Ecosystem
- Composer (PHP)
- Affected
- >= 11.0.0, <= 11.5.36
- Fixed in
- 11.5.37
- Check
composer show typo3/cms-core
typo3/cms-core
- Ecosystem
- Composer (PHP)
- Affected
- >= 12.0.0, <= 12.4.14
- Fixed in
- 12.4.15
- Check
composer show typo3/cms-core
typo3/cms-core
- Ecosystem
- Composer (PHP)
- Affected
- >= 13.0.0, <= 13.1.0
- Fixed in
- 13.1.1
- Check
composer show typo3/cms-core
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Problem
The ShowImageController (_eID tx_cms_showpic_) lacks a cryptographic HMAC-signature on the frame HTTP query parameter (e.g. /index.php?eID=tx_cms_showpic?file=3&...&frame=12345). This allows adversaries to instruct the system to produce an arbitrary number of thumbnail images on the server side.
Solution
Update to TYPO3 versions 9.5.48 ELTS, 10.4.45 ELTS, 11.5.37 LTS, 12.4.15 LTS, 13.1.1 that fix the problem described.
ℹ️ Strong security defaults - Manual actions required
The frame HTTP query parameter is now ignored, since it could not be used by core APIs.
The new feature flag security.frontend.allowInsecureFrameOptionInShowImageController – which is disabled per default – can be used to reactivate the previous behavior.
Credits
Thanks to TYPO3 security team member Torben Hansen who reported this issue and to TYPO3 core & security team members Benjamin Mack and Benjamin Franzke who fixed the issue.
References
Credited to derhansen, bnf, bmack.
References
- https://github.com/TYPO3/typo3/security/advisories/GHSA-36g8-62qv-5957
- https://nvd.nist.gov/vuln/detail/CVE-2024-34358
- https://github.com/TYPO3/typo3/commit/05c95fed869a1a6dcca06c7077b83b6ea866ff14
- https://github.com/TYPO3/typo3/commit/1e70ebf736935413b0531004839362b4fb0755a5
- https://github.com/TYPO3/typo3/commit/df7909b6a1cf0f12a42994d0cc3376b607746142
- https://typo3.org/security/advisory/typo3-core-sa-2024-010
- https://github.com/advisories/GHSA-36g8-62qv-5957
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-19418
TYPO3 CMS - Broken Access Control in Backend and Install Tool
high7.3Sep 1, 2026CVE-2026-11607
TYPO3 CMS has Broken Access Control in its Form Framework
high7.6Jun 12, 2026CVE-2026-47343
TYPO3 CMS: Destructive Actions on File Mount Folders
high7.2Jun 12, 2026CVE-2026-47346
TYPO3 CMS has Broken Access Control in its Form Framework
high7.6Jun 12, 2026CVE-2026-47347
TYPO3 CMS has an Open Redirect Vulnerability via Core Utilities
medium5.3Jun 12, 2026CVE-2026-47348
TYPO3 CMS has Cross-Site Scripting in Indexed Search
medium5.1Jun 12, 2026
