Advisory

GHSA-ppgf-8745-8pgx

Also known as: None

Summary

Insecure Deserialization & Arbitrary Code Execution in TYPO3 CMS

Details

Phar files (formerly known as "PHP archives") can act als self extracting archives which leads to the fact that source code is executed when Phar files are invoked. The Phar file format is not limited to be stored with a dedicated file extension - "bundle.phar" would be valid as well as "bundle.txt" would be. This way, Phar files can be obfuscated as image or text file which would not be denied from being uploaded and persisted to a TYPO3 installation. Due to a missing sanitization of user input, those Phar files can be invoked by manipulated URLs in TYPO3 backend forms. A valid backend user account is needed to exploit this vulnerability. In theory the attack vector would be possible in the TYPO3 frontend as well, however no functional exploit has been identified so far.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2024-06-05 16:41 UTC
Modified
2024-12-02 05:29 UTC

Affected packages and fixes

typo3/cms

Packagist · All systems

Affected

  • introduced 7.0.0, fixed 7.6.30 (ecosystem)

Fixed versions

7.6.30

Fix

The export has no generic command for this ecosystem.

typo3/cms

Packagist · All systems

Affected

  • introduced 8.0.0, fixed 8.7.17 (ecosystem)

Fixed versions

8.7.17

Fix

The export has no generic command for this ecosystem.

typo3/cms

Packagist · All systems

Affected

  • introduced 9.0.0, fixed 9.3.2 (ecosystem)

Fixed versions

9.3.2

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