TYPO3 CMS - Broken Access Control in File Abstraction Layer
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 10.4.57, 11.5.51, 12.4.46, 13.4.31, 14.3.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The path allowance check in GeneralUtility::isAllowedAbsPath() performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like /var/www/html-other/secret.yaml to be incorrectly accepted as valid when the project root was /var/www/html. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check. This issue affects TYPO3 CMS versions before 10.4.57, 11.0.0-11.5.50, 12.0.0-12.4.45, 13.0.0-13.4.30 and 14.0.0-14.3.2.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- typo3/cms-core
fixed in 10.4.57; From 11.0.0 · fixed in 11.5.51; From 12.0.0 · fixed in 12.4.46; From 13.0.0 · fixed in 13.4.31; From 14.0.0 · fixed in 14.3.3
- typo3/cms-corePackagist
fixed in 10.4.57
- typo3/cms-corePackagist
From 11.0.0 · fixed in 11.5.51
- typo3/cms-corePackagist
From 12.0.0 · fixed in 12.4.46
- typo3/cms-corePackagist
From 13.0.0 · fixed in 13.4.31
- typo3/cms-corePackagist
From 14.0.0 · fixed in 14.3.3