CVE-2022-36104

Meta

• CVSS: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H/E:F/RL:O/RC:C (5.5)

Problem

Requesting invalid or non-existing resources via HTTP triggers the page error handler which again could retrieve content to be shown as an error message from another page. This leads to a scenario in which the application is calling itself recursively - amplifying the impact of the initial attack until the limits of the web server are exceeded.

This vulnerability is the same as described in TYPO3-CORE-SA-2021-005 (CVE-2021-21359). A regression, introduced during TYPO3 v11 development, led to this situation.

Credits

Thanks to Rik Willems who reported this issue and to TYPO3 core & security team member Oliver Hader who fixed the issue.

References

• TYPO3-CORE-SA-2022-006

The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.

CVE-2022-36104 has a CVSS score of 5.9 (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 (11.5.16); upgrading removes the vulnerable code path.

Kodem intelligence

Update to TYPO3 version 11.5.16 that fixes the problem described above.

1. What is CVE-2022-36104? CVE-2022-36104 is a medium-severity allocation of resources without limits or throttling vulnerability in typo3/cms-core (composer), affecting versions >= 11.4.0, < 11.5.16. It is fixed in 11.5.16. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
2. How severe is CVE-2022-36104? CVE-2022-36104 has a CVSS score of 5.9 (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 packages are affected by CVE-2022-36104?
   • typo3/cms-core (composer) (versions >= 11.4.0, < 11.5.16)
   • typo3/cms (composer) (versions >= 11.4.0, < 11.5.16)
4. Is there a fix for CVE-2022-36104? Yes. CVE-2022-36104 is fixed in 11.5.16. Upgrade to this version or later.
5. Is CVE-2022-36104 exploitable, and should I be worried? Whether CVE-2022-36104 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-2022-36104 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-2022-36104?
   • Upgrade typo3/cms-core to 11.5.16 or later
   • Upgrade typo3/cms to 11.5.16 or later