Path Traversal in TYPO3 File Abstraction Layer Storages
Impact
Configurable storages using the local driver of the File Abstraction Layer (FAL) could be configured to access directories outside of the root directory of the corresponding project. The system setting in BE/lockRootPath was not evaluated by the file abstraction layer component. An administrator-level backend user account is required to exploit this vulnerability.
Source excerpt · OSVAffected packages
Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.
| Affected range | Recorded fix |
|---|---|
| From 8.0.0 before 8.7.57Ecosystem versions | 8.7.57 |
| From 9.0.0 before 9.5.46Ecosystem versions | 9.5.46 |
| From 10.0.0 before 10.4.43Ecosystem versions | 10.4.43 |
| From 11.0.0 before 11.5.35Ecosystem versions | 11.5.35 |
| From 12.0.0 before 12.4.11Ecosystem versions | 12.4.11 |
| From 13.0.0 before 13.0.1Ecosystem versions | 13.0.1 |
Version evidence: OSV · GHSA-w6x2-jg8h-p6mp
View original version evidence (174 explicit versions)
Original source description
Problem
Configurable storages using the local driver of the File Abstraction Layer (FAL) could be configured to access directories outside of the root directory of the corresponding project. The system setting in BE/lockRootPath was not evaluated by the file abstraction layer component. An administrator-level backend user account is required to exploit this vulnerability.
Solution
Update to TYPO3 versions 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, 13.0.1 that fix the problem described.
ℹ️ Strong security defaults - Manual actions required
see Important: #102800 changelog
Assuming that a web project is located in the directory /var/www/example.org (the "project root path" for Composer-based projects) and the publicly accessible directory is located at /var/www/example.org/public (the "public root path"), accessing resources via the File Abstraction Layer component is limited to the mentioned directories.
To grant additional access to directories, they must be explicitly configured in the system settings of $GLOBALS['TYPO3_CONF_VARS']['BE']['lockRootPath'] - either using the Install Tool or according to deployment techniques. The existing setting has been extended to support multiple directories configured as an array of strings.
Example:
$GLOBALS['TYPO3_CONF_VARS']['BE']['lockRootPath'] = [
‘/var/shared/documents/’,
‘/var/shared/images/’,
];
❗ Storages that reference directories not explicitly granted will be marked as "offline" internally - no resources can be used in the website's frontend and backend context.
Credits
Thanks to TYPO3 core & security team members Oliver Hader and Benjamin Franzke who fixed the issue.
References
References
- Security advisory github.com/TYPO3/typo3/security/advisories/GHSA-w6x2-jg8h-p6mp
- Security advisory nvd.nist.gov/vuln/detail/CVE-2023-30451
- Patch github.com/TYPO3/typo3/commit/205115cca3d67594a12d0195c937da0e51eb494a
- Patch github.com/TYPO3/typo3/commit/78fb9287a2f0487c39288070cb0493a5265f1789
- Patch github.com/TYPO3/typo3/commit/accf537c7379b4359bc0f957c4d0c07baddd710a
- Source reference github.com/TYPO3/typo3
- Security advisory typo3.org/security/advisory/typo3-core-sa-2024-001
- Public exploit reference packetstormsecurity.com/files/176274/TYPO3-11.5.24-Path-Traversal.html