TYPO3 up to 11.5.15 Error Message allocation of resources

Summaryinfo

A vulnerability classified as problematic has been found in TYPO3 up to 11.5.15. Affected by this vulnerability is an unknown functionality of the component Error Message Handler. The manipulation leads to allocation of resources. This vulnerability is documented as CVE-2022-36104. The attack can be initiated remotely. There is not any exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in TYPO3 up to 11.5.15 (Content Management System) and classified as problematic. This issue affects some unknown processing of the component Error Message Handler. The manipulation with an unknown input leads to a allocation of resources vulnerability. Using CWE to declare the problem leads to CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. Impacted is availability. The summary by CVE is:

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.

The weakness was released 09/14/2022 as GHSA-fffr-7x4x-f98q. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2022-36104 since 07/15/2022. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.

Upgrading to version 11.5.16 eliminates this vulnerability. Applying the patch 179dd7cd78947081d573fee2050e197faa556f13 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Content Management System

Name

• TYPO3

Version

• 11.5.0
• 11.5.1
• 11.5.2
• 11.5.3
• 11.5.4
• 11.5.5
• 11.5.6
• 11.5.7
• 11.5.8
• 11.5.9
• 11.5.10
• 11.5.11
• 11.5.12
• 11.5.13
• 11.5.14
• 11.5.15

License

• open-source

Website

• Product: https://typo3.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion