Описание
TYPO3 CMS vulnerable to Denial of Service in Page Error Handling
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
Ссылки
- https://github.com/TYPO3/typo3/security/advisories/GHSA-fffr-7x4x-f98q
- https://nvd.nist.gov/vuln/detail/CVE-2022-36104
- https://github.com/TYPO3/typo3/commit/179dd7cd78947081d573fee2050e197faa556f13
- https://github.com/TYPO3/typo3/commit/fc51ccbf2bb8a8c959aa74cbceca124971e6e7fd
- https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2022-36104.yaml
- https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/CVE-2022-36104.yaml
- https://typo3.org/security/advisory/typo3-core-sa-2022-006
Пакеты
typo3/cms-core
>= 11.4.0, < 11.5.16
11.5.16
typo3/cms
>= 11.4.0, < 11.5.16
11.5.16
Связанные уязвимости
TYPO3 is an open source PHP based web content management system released under the GNU GPL. In affected versions 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. Users are advised to update to TYPO3 version 11.5.16 to resolve this issue. There are no known workarounds for this issue.