GHSA-8h4m-r4wm-xj7r json
TYPO3 Arbitrary Code Execution via File List Module
published 2y ago modified last yr.
- cvss
- 8.8
- 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
Due to missing file extensions in $GLOBALS['TYPO3_CONF_VARS']['BE'][‘fileDenyPattern’], backend users are allowed to upload *.phar, *.shtml, *.pl or *.cgi files which can be executed in certain web server setups. A valid backend user account is needed in order to exploit this vulnerability.
Derivatives of Debian GNU Linux are handling *.phar files as PHP applications since PHP 7.1 (for unofficial packages) and PHP 7.2 (for official packages).
The file extension *.shtml is bound to server side includes which are not enabled per default in most common Linux based distributions. File extension *.pl and *.cgi require additional handlers to be configured which is also not the case in most common distributions (except for /cgi-bin/ location).
Patch / fix
- packagist typo3/cms 8.7.23, 9.5.4
- github.com/TYPO3/typo3@095ae4a commit
- github.com/TYPO3/typo3@9990278 commit
Is GHSA-8h4m-r4wm-xj7r 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 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | typo3/cms | >=8.0.0, <8.7.23 >=9.0.0, <9.5.4 |
8.7.23 9.5.4 |
Classification
- Weakness
-
- CWE-434 Unrestricted Upload of File with Dangerous Type
References
-
github.com
/TYPO3/typo3/commit/095ae4ab6869d0f7dc7befedb851cdd7ad0c7ebf
web
-
github.com
/TYPO3/typo3/commit/9990278ce7cf8e4d6b8bf31edec6787722d38b0f
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/typo3/cms/2019-01-22-7.yaml
web
-
github.com
/TYPO3/typo3
package
-
typo3.org
/security/advisory/typo3-core-sa-2019-008
web
Sources
- GitHub Advisory GHSA-8h4m-r4wm-xj7r
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.