TYPO3 CMS - Broken Access Control in File Abstraction Layer
TYPO3 CMS
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| typo3/cms-core Packagist |
|
|
TYPO3 CMS
| Product | Affected | Fixed in |
|---|---|---|
| typo3/cms-core Packagist |
|
|
13.4.3114.3.3The 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.
From the CVE record · TYPO3
GeneralUtility::isAllowedAbsPath() accepts paths outside the project root when they share its string prefix. An administrator with File Abstraction Layer access can create a file storage definition pointing to such a directory, bypassing the path check.
Operators running TYPO3 CMS with typo3/cms-core before 10.4.57, from 11.0.0 to 11.5.50, from 12.0.0 to 12.4.45, from 13.0.0 to 13.4.30, or from 14.0.0 to 14.3.2 should check.