MediumGHSA-36g8-62qv-5957CVE-2024-34358

TYPO3 vulnerable to an Uncontrolled Resource Consumption in the ShowImageController

Published 14 May 2024 · Updated 10 Sept 2026

Affected packages

typo3/cms-coreComposer
Affected
>=9.0.0 <9.5.48
Fixed in
9.5.48
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^9.5.48
typo3/cms-coreComposer
Affected
>=10.0.0 <10.4.45
Fixed in
10.4.45
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^10.4.45
typo3/cms-coreComposer
Affected
>=11.0.0 <11.5.37
Fixed in
11.5.37
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^11.5.37
typo3/cms-coreComposer
Affected
>=12.0.0 <12.4.15
Fixed in
12.4.15
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^12.4.15
typo3/cms-coreComposer
Affected
>=13.0.0 <13.1.1
Fixed in
13.1.1
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^13.1.1

Details

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

Is GHSA-36g8-62qv-5957 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected typo3/cms-core, and gives you the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.