Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

github логотип

GHSA-2r6j-862c-m2v2

Опубликовано: 23 мар. 2021
Источник: github
Github: Прошло ревью
CVSS3: 8.6

Описание

Unrestricted File Upload in Form Framework

Problem

Due to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default fileDenyPattern successfully blocked files like .htaccess or malicious.php.

TYPO3 Extbase extensions, which implement a file upload and do not implement a custom TypeConverter to transform uploaded files into FileReference domain model objects are affected by the vulnerability as well, since the UploadedFileReferenceConverter of ext:form handles the file upload and will accept files of any mime-type which are persisted to the default location.

In any way, uploaded files are placed in the default location /fileadmin/user_upload/, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.

No authentication is required to exploit this vulnerability.

Solution

Update to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.

Type converter UploadedFileReferenceConverter is not registered globally anymore and just handles uploaded files within the scope of the Form Framework. Guessable storage location has changed from /fileadmin/user_upload/form_<random-hash>/ to /fileadmin/form_uploads/. Allowed mime-types must match expected file extensions (e.g. application/pdf must be .pdf, and cannot be .html).

Extbase extensions, who rely on the global availability of the UploadedFileReferenceConverter must now implement a custom TypeConverter to handle file uploads or explicitly implement the ext:form UploadedFileReferenceConverter with appropriate setting for accepted mime-types.

Credits

Thanks to Sebastian Michaelsen, Marc Lindemann, Oliver Eglseder, Markus Volkmer, Jakob Kunzmann, Johannes Regner, Richie Lee who reported this issue, and to TYPO3 core & security team members Oliver Hader & Benni Mack, as well as TYPO3 contributor Ralf Zimmermann who fixed the issue.

References

Пакеты

Наименование

typo3/cms-form

composer
Затронутые версииВерсия исправления

>= 8.0.0, <= 8.7.39

8.7.40

Наименование

typo3/cms-form

composer
Затронутые версииВерсия исправления

>= 9.0.0, <= 9.5.24

9.5.25

Наименование

typo3/cms-form

composer
Затронутые версииВерсия исправления

>= 10.0.0, <= 10.4.13

10.4.14

Наименование

typo3/cms-form

composer
Затронутые версииВерсия исправления

>= 11.0.0, <= 11.1.0

11.1.1

Наименование

typo3/cms-core

composer
Затронутые версииВерсия исправления

>= 10.0.0, < 10.4.14

10.4.14

Наименование

typo3/cms-core

composer
Затронутые версииВерсия исправления

>= 11.0.0, < 11.1.1

11.1.1

Наименование

typo3/cms-core

composer
Затронутые версииВерсия исправления

>= 9.0.0, < 9.5.25

9.5.25

Наименование

typo3/cms

composer
Затронутые версииВерсия исправления

>= 10.0.0, < 10.4.14

10.4.14

Наименование

typo3/cms

composer
Затронутые версииВерсия исправления

>= 11.0.0, < 11.1.1

11.1.1

Наименование

typo3/cms

composer
Затронутые версииВерсия исправления

>= 9.0.0, < 9.5.25

9.5.25

EPSS

Процентиль: 61%
0.00416
Низкий

8.6 High

CVSS3

Дефекты

CWE-434
CWE-552

Связанные уязвимости

CVSS3: 8.6
nvd
почти 5 лет назад

TYPO3 is an open source PHP based web content management system. In TYPO3 before versions 8.7.40, 9.5.25, 10.4.14, 11.1.1, due to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_. Besides that, _UploadedFileReferenceConverter_ transforming uploaded files into proper FileReference domain model objects handles possible file uploads for other extensions as well - given those extensions use the Extbase MVC framework, make use of FileReference items in their direct or inherited domain model definitions and did not implement their own type converter. In case this scenario applies, _UploadedFileReferenceConverter_ accepts any file mime-type and persists files in the default location. In any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the

EPSS

Процентиль: 61%
0.00416
Низкий

8.6 High

CVSS3

Дефекты

CWE-434
CWE-552