CVE-2024-34358

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.

ℹ️ 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

• TYPO3-CORE-SA-2024-010

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

CVE-2024-34358 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (9.5.48, 10.4.45, 11.5.37, 12.4.15, 13.1.1); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is CVE-2024-34358? CVE-2024-34358 is a medium-severity uncontrolled resource consumption vulnerability in typo3/cms-core (composer), affecting versions >= 9.0.0, <= 9.5.47. It is fixed in 9.5.48, 10.4.45, 11.5.37, 12.4.15, 13.1.1. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
2. How severe is CVE-2024-34358? CVE-2024-34358 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of typo3/cms-core are affected by CVE-2024-34358? typo3/cms-core (composer) versions >= 9.0.0, <= 9.5.47 is affected.
4. Is there a fix for CVE-2024-34358? Yes. CVE-2024-34358 is fixed in 9.5.48, 10.4.45, 11.5.37, 12.4.15, 13.1.1. Upgrade to this version or later.
5. Is CVE-2024-34358 exploitable, and should I be worried? Whether CVE-2024-34358 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-34358 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-34358?
   • Upgrade typo3/cms-core to 9.5.48 or later
   • Upgrade typo3/cms-core to 10.4.45 or later
   • Upgrade typo3/cms-core to 11.5.37 or later
   • Upgrade typo3/cms-core to 12.4.15 or later
   • Upgrade typo3/cms-core to 13.1.1 or later