Skip to content

Path Traversal in TYPO3 File Abstraction Layer Storages

Moderate severity GitHub Reviewed Published Feb 13, 2024 in TYPO3/typo3 • Updated Feb 20, 2024

Package

composer typo3/cms-core (Composer)

Affected versions

>= 8.0.0, <= 8.7.56
>= 9.0.0, <= 9.5.45
>= 10.0.0, <= 10.4.42
>= 11.0.0, <= 11.5.34
>= 12.0.0, <= 12.4.10
= 13.0.0

Patched versions

8.7.57
9.5.46
10.4.43
11.5.35
12.4.11
13.0.1

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

@ohader ohader published to TYPO3/typo3 Feb 13, 2024
Published to the GitHub Advisory Database Feb 13, 2024
Reviewed Feb 13, 2024
Last updated Feb 20, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N

EPSS score

0.051%
(21st percentile)

Weaknesses

CVE ID

CVE-2023-30451

GHSA ID

GHSA-w6x2-jg8h-p6mp

Source code

Credits

  • @ohader ohader Remediation developer
  • @bnf bnf Remediation reviewer
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.