Anmelden
Deutsch English Español Polski
Hoch

Unrestricted File Upload in Form Framework

  • Veröffentlicht: 23.03.2021
  • Aktualisiert: 11.10.2026 10:22

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/<random-40-bit>. 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

Betroffene Software

Klicken Sie auf eine Technologie, um alle zugehörigen Schwachstellen anzuzeigen.

PlattformPaketAnfällige VersionenBehoben in
Composer-Paket typo3/cms >= 10.0.0, < 10.4.14, >= 11.0.0, < 11.1.1, >= 9.0.0, < 9.5.25 10.4.14, 11.1.1, 9.5.25
Composer-Paket typo3/cms-core >= 10.0.0, < 10.4.14, >= 11.0.0, < 11.1.1, >= 9.0.0, < 9.5.25 10.4.14, 11.1.1, 9.5.25
Composer-Paket typo3/cms-form >= 8.0.0, < 8.7.40, >= 9.0.0, < 9.5.25, >= 10.0.0, < 10.4.14, >= 11.0.0, < 11.1.1 8.7.40, 9.5.25, 10.4.14, 11.1.1

Verweise

CVSS-Wert 8.6/10
CVSS-Vektor
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L/E:F/RL:O/RC:C
Schwäche (CWE)
CWE-434, CWE-552
Plattform
Composer
Paket
typo3/cms, typo3/cms-core, typo3/cms-form
Veröffentlicht
23.03.2021
Aktualisiert
11.10.2026 10:22

Quellen und Lizenzen

OSV / GitHub Advisory Database - GHSA-2r6j-862c-m2v2 - CC BY 4.0

Schwachstellenhistorie: typo3/cms

Alle veröffentlichten Schwachstellen dieses Pakets (Composer-Paket), neueste zuerst. Zeigt, ob es ein einmaliger Ausrutscher ist oder ein Paket, das man im Auge behalten muss.

Alle (188) im Archiv
Einträge insgesamt
188
Erste → letzte
09.2018 06.2024
Ohne Fix
3
In Angriffen ausgenutzt
0

Verteilung nach Schweregrad

  • Kritisch 6
  • Hoch 41
  • Mittel 128
  • Niedrig 13

Veröffentlichungen pro Jahr

Schweregrad:
  1. TYPO3 Security Misconfiguration in Install Tool Cookie
    Hoch · 8.1 ghsa-f777-f784-36gm >= 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
  2. TYPO3 Arbitrary Code Execution via File List Module
    Hoch · 8.8 ghsa-8h4m-r4wm-xj7r >= 8.0.0, < 8.7.23, >= 9.0.0, < 9.5.4 8.7.23, 9.5.4
  3. TYPO3 Denial of Service in Frontend Record Registration
    Hoch · 7.5 ghsa-g585-crjf-vhwq >= 7.0.0, < 7.6.32, >= 8.0.0, < 8.7.21 7.6.32, 8.7.21
  4. TYPO3 Security Misconfiguration for Backend User Accounts
    Hoch · 7.3 ghsa-c5mj-39cf-3pp5 >= 8.0.0, < 8.7.23, >= 9.0.0, < 9.5.4 8.7.23, 9.5.4
  5. TYPO3 CMS Possible Insecure Deserialization in Extbase Request Handling
    Hoch · 8.1 ghsa-hh95-5xm5-v8v7 >= 8.0.0, < 8.7.30, >= 9.0.0, < 9.5.12 8.7.30, 9.5.12
  6. Insecure Deserialization & Arbitrary Code Execution in TYPO3 CMS
    Hoch ghsa-ppgf-8745-8pgx >= 7.0.0, < 7.6.30, >= 8.0.0, < 8.7.17, >= 9.0.0, < 9.3.2 7.6.30, 8.7.17, 9.3.2
  7. Privilege Escalation & SQL Injection in TYPO3 CMS
    Hoch · 8.8 ghsa-7qwg-fcpw-xg5g >= 8.5.0, < 8.7.17, >= 9.0.0, < 9.3.2 8.7.17, 9.3.2
  8. TYPO3 Remote Code Execution in third party library swiftmailer
    Hoch ghsa-g4pf-3jvq-2gcw >= 6.2.0, < 6.2.30, >= 7.6.0, < 7.6.15, >= 8.0.0, < 8.5.1 6.2.30, 7.6.15, 8.5.1
  9. Arbitrary Code Execution in TYPO3 CMS
    Kritisch · 9.9 ghsa-67wg-6j7r-mqh8 >= 7.6.0, < 7.6.22, >= 8.0.0, < 8.7.5 7.6.22, 8.7.5
  10. Insecure Deserialization in TYPO3 CMS
    Hoch ghsa-8h28-f46f-m87h >= 8.5.0, < 8.7.17, >= 9.0.0, < 9.3.2 8.7.17, 9.3.2
  11. Missing Access Check in TYPO3 CMS
    Kritisch · 9.0 ghsa-gwfx-p7mr-f92v >= 6.2.0, < 6.2.25, >= 7.6.0, < 7.6.8, >= 8.0.0, < 8.1.1 6.2.25, 7.6.8, 8.1.1
  12. XML External Entity (XXE) Processing in TYPO3 Core
    Hoch ghsa-qffc-gwpp-m2xr >= 6.2.0, < 6.2.19, >= 7.6.0, < 7.6.4 6.2.19, 7.6.4
  13. TYPO3 SQL Injection in dbal
    Hoch ghsa-9895-53fc-98v2 >= 6.2.0, < 6.2.18 6.2.18
  14. TYPO3 frontend login vulnerable to Session Fixation
    Hoch · 7.1 ghsa-r9vc-jfmh-6j48 >= 6.2.0, < 6.2.14, >= 7.0.0, < 7.3.1 6.2.14, 7.3.1
  15. TYPO3 may allow editors to change, create, or delete metadata of files not within their file mounts
    Hoch · 8.8 ghsa-4r76-xr68-w7m7 >= 6.2.0, < 6.2.14, >= 7.0.0, < 7.3.1 6.2.14, 7.3.1
  16. TYPO3 possible cache poisoning on the homepage when anchors are used
    Hoch ghsa-p84g-j2gh-83g3 >= 6.2.0, < 6.2.9, >= 7.0.0, < 7.0.2 6.2.9, 7.0.2
  17. TYPO3 Arbitrary Shell Execution in Swiftmailer library
    Hoch · 8.1 ghsa-45xg-4w5x-j429 >= 6.2.0, < 6.2.6, >= 6.1.0, < 6.1.12, >= 4.7.0, < 4.7.20, >= 4.5.0, < 4.5.37 6.2.6, 6.1.12, 4.7.20, 4.5.37
  18. TYPO3 is vulnerable to Cross-Site Scripting via frontend rendering
    Hoch · 8.8 CVE-2023-24814 >= 10.0.0, < 10.4.35, >= 11.0.0, < 11.5.23, >= 12.0.0, < 12.2.0 10.4.35, 11.5.23, 12.2.0
  19. TYPO3 vulnerable to Insufficient Session Expiration
    Kritisch · 9.8 CVE-2022-47406 < 2.0.5, >= 3.0.0, < 3.0.3 2.0.5, 3.0.3
  20. TYPO3 CMS vulnerable to Arbitrary Code Execution via Form Framework
    Hoch · 7.5 CVE-2022-23503 >= 10.0.0, < 10.4.33, >= 11.0.0, < 11.5.20, >= 12.0.0, < 12.1.1 10.4.33, 11.5.20, 12.1.1
  21. TYPO3 Vulnerable to Insecure Deserialization
    Hoch · 8.8 CVE-2019-12747 >= 8.0.0, < 8.7.27, >= 9.0.0, < 9.5.8 8.7.27, 9.5.8
  22. TYPO3 Image Processing susceptible to Code Execution
    Hoch · 7.5 CVE-2019-11832 >= 8.0.0, < 8.7.25, >= 9.0.0, < 9.5.6 8.7.25, 9.5.6
  23. TYPO3 Insecure Deserialization in Query Generator & Query View
    Hoch · 8.8 CVE-2019-19849 >= 10.0.0, < 10.2.1, >= 8.0.0, < 8.7.30, >= 9.0.0, < 9.5.12 10.2.1, 8.7.30, 9.5.12
  24. TYPO3 Remote File Disclosure vulnerability in the jumpUrl mechanism
    Hoch CVE-2010-3714 >= 4.2.0, < 4.2.15, >= 4.3.0, < 4.3.7, >= 4.4.0, < 4.4.4 4.2.15, 4.3.7, 4.4.4
  25. TYPO3 vulnerable to remote authenticated arbitrary code execution
    Hoch CVE-2013-4321 >= 6.0.0, < 6.0.9, >= 6.1.0, < 6.1.4 6.0.9, 6.1.4
  26. TYPO3 doesn't properly check file extensions
    Hoch CVE-2013-4250 >= 6.0.0, < 6.0.8, >= 6.1.0, < 6.1.3 6.0.8, 6.1.3
  27. TYPO3 vulnerable to authentication bypass via leveraging knowledge of password hash
    Kritisch CVE-2014-3945 < 6.2.0 6.2.0
  28. Typo3 Vulnerable to Cache Poisoning
    Hoch CVE-2014-9509 >= 4.5.0, < 4.5.39, >= 6.2.0, < 6.2.9, >= 7.0.0, < 7.0.2, >= 4.6.0, < 4.6.19, >= 4.7.0, < 4.7.21, >= 6.0.0, < 6.0.15, >= 6.1.0, < 6.1.13 4.5.39, 6.2.9, 7.0.2, 4.6.19, 4.7.21, 6.0.15, 6.1.13
  29. PHP OpenID Library Denial of Service vulnerability
    Hoch CVE-2013-4701 >= 6.2.0, < 6.2.6 6.2.6
  30. TYPO3 Arbitrary Code Execution
    Hoch · 8.8 CVE-2017-14251 >= 7.6.0, < 7.6.22, >= 8.0.0, < 8.7.5 7.6.22, 8.7.5
  31. TYPO3 Color Picker Wizard component allows remote authenticated editors to execute arbitrary PHP code
    Hoch CVE-2014-3942 >= 4.5.0, < 4.5.34, >= 4.7.0, < 4.7.19, >= 6.0.0, < 6.0.14, >= 6.1.0, < 6.1.9 4.5.34, 4.7.19, 6.0.14, 6.1.9
  32. TYPO3 PHP remote file inclusion vulnerability
    Hoch CVE-2010-1153 >= 4.3.0, < 4.3.3 4.3.3
  33. Indexed Search Engine for TYPO3 Command Execution via Metacharacter Injection
    Hoch CVE-2009-0258 >= 4.0.0, < 4.0.10, >= 4.1.0, < 4.1.8, >= 4.2.0, < 4.2.4 4.0.10, 4.1.8, 4.2.4
  34. Authentication library in TYPO3 vulnerable to session fixation
    Hoch CVE-2009-0256 >= 4.0.0, < 4.0.10, >= 4.1.0, < 4.1.8, >= 4.2.0, < 4.2.4 4.0.10, 4.1.8, 4.2.4
  35. TYPO3 Reveals Sensitive Information via Direct Request to `misc/phpcheck/`
    Hoch CVE-2005-4875 < 3.8.1 3.8.1
  36. Typo3 SQL injection due to faulty prepared statements
    Kritisch · 9.8 CVE-2011-3583 >= 4.5.0, <= 4.5.5 keine Korrektur
  37. Typo3 Authentication Bypass
    Kritisch · 9.8 CVE-2011-4628 < 4.3.12, >= 4.4.0, < 4.4.9, >= 4.5.0, < 4.5.4 4.3.12, 4.4.9, 4.5.4
  38. Cross-Site-Request-Forgery in Backend
    Hoch · 8.8 CVE-2021-41113 >= 11.2.0, < 11.5.0 11.5.0
  39. Broken Access Control in Form Framework
    Hoch · 8.3 CVE-2021-21357 >= 10.0.0, < 10.4.14, >= 11.0.0, < 11.1.1, >= 9.0.0, < 9.5.25 10.4.14, 11.1.1, 9.5.25
  40. Unrestricted File Upload in Form Framework dieser Eintrag
    Hoch · 8.6 CVE-2021-21355 >= 10.0.0, < 10.4.14, >= 11.0.0, < 11.1.1, >= 9.0.0, < 9.5.25 10.4.14, 11.1.1, 9.5.25
  41. Cleartext storage of session identifier
    Hoch · 8.1 CVE-2020-26228 >= 10.0.0, < 10.4.10, >= 9.0.0, < 9.5.23, >= 8.7.0, < 8.7.38 10.4.10, 9.5.23, 8.7.38
  42. Exposure of Sensitive Information to an Unauthorized Actor in TYPO3 CMS
    Hoch · 8.1 CVE-2020-15099 >= 10.0.0, < 10.4.6, >= 9.0.0, < 9.5.20 10.4.6, 9.5.20
  43. Missing Required Cryptographic Step Leading to Sensitive Information Disclosure in TYPO3 CMS
    Hoch · 8.8 CVE-2020-15098 >= 10.0.0, < 10.4.6, >= 9.0.0, < 9.5.20 10.4.6, 9.5.20
  44. Backend Same-Site Request Forgery in TYPO3 CMS
    Hoch · 8.0 CVE-2020-11069 >= 10.0.0, < 10.4.2, >= 9.0.0, < 9.5.17 10.4.2, 9.5.17
  45. Insecure Deserialization in Backend User Settings in TYPO3 CMS
    Hoch · 8.8 CVE-2020-11067 >= 10.0.0, < 10.4.2, >= 9.0.0, < 9.5.17 10.4.2, 9.5.17
  46. Class destructors causing side-effects when being unserialized in TYPO3 CMS
    Hoch · 8.7 CVE-2020-11066 >= 10.0.0, < 10.4.2, >= 9.0.0, < 9.5.17 10.4.2, 9.5.17
  47. Deserialization of untrusted data in Symfony
    Hoch · 7.1 CVE-2019-10912 >= 9.0.0, < 9.5.8 9.5.8

Erkennen Sie Schwachstellen in Ihrer Anwendung

Mit der DockRay-Integration und aktivierter Softwareinventarisierung prüft DockRay gemeldete Komponentenversionen auf bekannte Schwachstellen und benachrichtigt Sie über bestätigte Treffer. Die Abdeckung hängt von der unterstützten Technologie und den verfügbaren Meldungen ab.

Anwendung verbinden
DockRay Newsletter

Anwendungssicherheit in Ihrem Postfach

Wichtige Schwachstellen, konkrete Empfehlungen und praktische Tipps für Ihre Anwendungen. Wählen Sie Ihre Technologien und verfolgen Sie, was für Ihr Projekt relevant ist.

  • Eine tägliche Zusammenfassung neuer Schwachstellen, auch kritischer.
  • Benachrichtigungen über wichtige Updates.
  • Praktische Tipps zur Sicherheit und Überwachung von Anwendungen.

Leer lassen, um Meldungen zu allen Technologien zu erhalten.

Datenschutzerklärung

Kostenlos anmelden. In jeder E-Mail mit einem Klick abmelden.