| Package | Affected versions | Patched versions |
|---|---|---|
| typo3/cms | ≥ 10.0.0, < 10.4.14≥ 11.0.0, < 11.1.1≥ 9.0.0, < 9.5.25 | 10.4.1411.1.19.5.25 |
| typo3/cms-core | ≥ 10.0.0, < 10.4.14≥ 11.0.0, < 11.1.1≥ 9.0.0, < 9.5.25 | 10.4.1411.1.19.5.25 |
| typo3 | ≥ 10.0.0, < 10.4.14≥ 11.0.0, < 11.1.1≥ 9.0.0, < 9.5.25 | 10.4.1411.1.19.5.25 |
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
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.
Update to TYPO3 versions 9.5.25, 10.4.14, 11.1.1 that fix the problem described.
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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free