MediumGHSA-fffr-7x4x-f98qBIT-typo3-2022-36104CVE-2022-36104

TYPO3 CMS vulnerable to Denial of Service in Page Error Handling

Published 16 Sept 2022 · Updated 6 Dec 2023

Affected packages

typo3/cms-coreComposer
Affected
>=11.4.0 <11.5.16
Fixed in
11.5.16
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^11.5.16
typo3/cmsComposer
Affected
>=11.4.0 <11.5.16
Fixed in
11.5.16
Update to the fixed version for your release line, for example:composer require typo3/cms:^11.5.16

Details

> ### 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.

Solution

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

Credits

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

References

Is GHSA-fffr-7x4x-f98q 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.