Skip to content
Log inStart free trial

GHSA-rj3x-wvc6-5j66 CVE-2024-25121

TYPO3 vulnerable to Improper Access Control Persisting File Abstraction Layer Entities via Data Handler

High Packagist
Severity
7.1 / 10
High · CVSS 3.1
Exploit chance (EPSS)
0.50%
Chance of exploitation in the next 30 days. Higher than 42.59% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-284 Improper Access Control
Fix
8.7.57
Upgrade typo3/cms-core to this version or later

Description

Problem

Entities of the File Abstraction Layer (FAL) could be persisted directly via DataHandler. This allowed attackers to reference files in the fallback storage directly and retrieve their file names and contents. The fallback storage ("zero-storage") is used as a backward compatibility layer for files located outside properly configured file storages and within the public web root directory. Exploiting this vulnerability requires a valid backend user account.

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

When persisting entities of the File Abstraction Layer directly via DataHandler, sys_file entities are now denied by default, and sys_file_reference & sys_file_metadata entities are not permitted to reference files in the fallback storage anymore.

When importing data from secure origins, this must be explicitly enabled in the corresponding DataHandler instance by using $dataHandler->isImporting = true;.

Credits

Thanks to TYPO3 core & security team member Oliver Hader who reported and fixed the issue.

References

Affected versions

Packagist

PackageVulnerableFixed in
typo3/cms-core
>= 8.0.0, < 8.7.57
8.7.57
typo3/cms-core
>= 9.0.0, < 9.5.46
9.5.46
typo3/cms-core
>= 10.0.0, < 10.4.43
10.4.43
typo3/cms-core
>= 11.0.0, < 11.5.35
11.5.35
typo3/cms-core
>= 12.0.0, < 12.4.11
12.4.11
typo3/cms-core
>= 13.0.0, < 13.0.1
13.0.1

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

typo3/cms-core Packagist → 8.7.57

composer
composer require typo3/cms-core:^8.7.57

Severity breakdown

CVSS 3.1 7.1

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

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

Weakness

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How to prevent it
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

CWE-284: Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

How to prevent it
  • Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Advisories

Packages

Other links

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-68jx-f42c-7599
TYPO3 CMS - Broken Access Control in Backend and Install Tool
High Also affects typo3/cms-core
GHSA-chm7-4vch-h8vr
TYPO3 CMS has Broken Access Control in its Media Module
High Also affects typo3/cms-core
GHSA-jh32-v29g-68pq
TYPO3 CMS has Privilege Escalation & SQL Injection in its Form Framework
High Also affects typo3/cms-core
GHSA-c78m-c52x-jgwp
TYPO3 CMS has Insecure Deserialization via Core API
Medium Also affects typo3/cms-core
GHSA-jf56-v8jc-jcc5
TYPO3 CMS has Broken Access Control in its File Abstraction Layer
Low Also affects typo3/cms-core
GHSA-2j54-93q2-3hjq
TYPO3 CMS has Broken Access Control in Backend API
Medium Also affects typo3/cms-core
GHSA-q93m-25xv-94hh
TYPO3 CMS: Broken Access Control in Media Module
Medium Also affects typo3/cms-core
GHSA-qcmw-6rm2-5x78
TYPO3 CMS has Broken Access Control in its DataHandler
Medium Also affects typo3/cms-core
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor