TYPO3 Denial of Service in Online Media Asset Handling
Published 7 Jun 2024 · Updated 4 Dec 2024
Affected packages
- Affected
- >=7.0.0 <7.6.32
- Fixed in
- 7.6.32
composer require typo3/cms:^7.6.32- Affected
- >=8.0.0 <8.7.21
- Fixed in
- 8.7.21
composer require typo3/cms:^8.7.21- Affected
- >=9.0.0 <9.5.2
- Fixed in
- 9.5.2
composer require typo3/cms:^9.5.2Details
Online Media Asset Handling (*.youtube and *.vimeo files) in the TYPO3 backend is vulnerable to denial of service. Putting large files with according file extensions results in high consumption of system resources. This can lead to exceeding limits of the current PHP process which results in a dysfunctional backend component. A valid backend user account or write access on the server system (e.g. SFTP) is needed in order to exploit this vulnerability.
Is GHSA-f3wf-q4fj-3gxf 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, and gives you the command that fixes it.
References
- Linkgithub.com/TYPO3/typo3/commit/054799caf53b28ff92e00aff957fab88c45a7509
- Linkgithub.com/TYPO3/typo3/commit/16567366e2a25c0cbed7208c3be9eda962e28c9b
- Linkgithub.com/TYPO3/typo3/commit/7a5155e0137d01db7e5723849f0493ad5b0c98ac
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/2018-12-11-6.yaml
- Packagegithub.com/TYPO3/typo3
- Linktypo3.org/security/advisory/typo3-core-sa-2018-011
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.