TYPO3 Arbitrary Code Execution via File List Module
Published 30 May 2024 · Updated 5 Dec 2024
Affected packages
- Affected
- >=8.0.0 <8.7.23
- Fixed in
- 8.7.23
composer require typo3/cms-core:^8.7.23- Affected
- >=9.0.0 <9.5.4
- Fixed in
- 9.5.4
composer require typo3/cms-core:^9.5.4Details
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).
Is GHSA-f9hr-7cfq-mjg2 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-core, and gives you the command that fixes it.
References
- Linkgithub.com/TYPO3-CMS/core/commit/45c311d120c359d54cc918e962c374e774239899
- Linkgithub.com/TYPO3-CMS/core/commit/5095084efae471c5fef7b578f2bc8a5060e1e148
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/2019-01-22-7.yaml
- Packagegithub.com/TYPO3-CMS/core
- Linktypo3.org/security/advisory/typo3-core-sa-2019-008
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.