Advisory

GHSA-w6x2-jg8h-p6mp

Also known as: BIT-typo3-2023-30451, CVE-2023-30451

Summary

Path Traversal in TYPO3 File Abstraction Layer Storages

Details

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

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2024-02-13 19:08 UTC
Modified
2024-02-20 15:21 UTC

Affected packages and fixes

typo3/cms-core

Packagist · All systems

Affected

  • introduced 8.0.0, fixed 8.7.57 (ecosystem)

Fixed versions

8.7.57

Fix

The export has no generic command for this ecosystem.

typo3/cms-core

Packagist · All systems

Affected

  • introduced 9.0.0, fixed 9.5.46 (ecosystem)

Fixed versions

9.5.46

Fix

The export has no generic command for this ecosystem.

typo3/cms-core

Packagist · All systems

Affected

  • introduced 10.0.0, fixed 10.4.43 (ecosystem)

Fixed versions

10.4.43

Fix

The export has no generic command for this ecosystem.

typo3/cms-core

Packagist · All systems

Affected

  • introduced 11.0.0, fixed 11.5.35 (ecosystem)

Fixed versions

11.5.35

Fix

The export has no generic command for this ecosystem.

typo3/cms-core

Packagist · All systems

Affected

  • introduced 12.0.0, fixed 12.4.11 (ecosystem)

Fixed versions

12.4.11

Fix

The export has no generic command for this ecosystem.

typo3/cms-core

Packagist · All systems

Affected

  • introduced 13.0.0, fixed 13.0.1 (ecosystem)

Fixed versions

13.0.1

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences