GHSA-f3wf-q4fj-3gxf json
TYPO3 Denial of Service in Online Media Asset Handling
published 2y ago modified last yr.
- cvss
- 6.5
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist typo3/cms 7.6.32, 8.7.21, 9.5.2
- github.com/TYPO3/typo3@054799c commit
- github.com/TYPO3/typo3@1656736 commit
- github.com/TYPO3/typo3@7a5155e commit
Is GHSA-f3wf-q4fj-3gxf in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | typo3/cms | >=7.0.0, <7.6.32 >=8.0.0, <8.7.21 >=9.0.0, <9.5.2 |
7.6.32 8.7.21 9.5.2 |
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
github.com
/TYPO3/typo3/commit/054799caf53b28ff92e00aff957fab88c45a7509
web
-
github.com
/TYPO3/typo3/commit/16567366e2a25c0cbed7208c3be9eda962e28c9b
web
-
github.com
/TYPO3/typo3/commit/7a5155e0137d01db7e5723849f0493ad5b0c98ac
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/typo3/cms/2018-12-11-6.yaml
web
-
github.com
/TYPO3/typo3
package
-
typo3.org
/security/advisory/typo3-core-sa-2018-011
web
Sources
- GitHub Advisory GHSA-f3wf-q4fj-3gxf
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.