typo3/cms-core
Affected
- introduced
10.0.0, fixed10.4.14(ecosystem)
Fixed versions
10.4.14
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: BIT-typo3-2021-21359, CVE-2021-21359
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)
> * CWE-405, CWE-674
> * Status: DRAFT
Problem
Requesting invalid or non-existing resources via HTTP triggers the page error handler which again could retrieve content to be shown as 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.
Solution
Update to TYPO3 versions 9.5.25, 10.4.14, 11.1.1 that fix the problem described.
Credits
Thanks to Paul Keller, Mathias Bolt Lesniak and Kay Strobach who reported this issue and to TYPO3 framework merger Frank Nägler and to TYPO3 security team member Torben Hansen who fixed the issue.
References
Medium Basis: The source's own band: MODERATE
10.0.0, fixed 10.4.14 (ecosystem)10.4.14
The export has no generic command for this ecosystem.
11.0.0, fixed 11.1.1 (ecosystem)11.1.1
The export has no generic command for this ecosystem.
9.0.0, fixed 9.5.25 (ecosystem)9.5.25
The export has no generic command for this ecosystem.
10.0.0, fixed 10.4.14 (ecosystem)10.4.14
The export has no generic command for this ecosystem.
11.0.0, fixed 11.1.1 (ecosystem)11.1.1
The export has no generic command for this ecosystem.
9.0.0, fixed 9.5.25 (ecosystem)9.5.25
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0