Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

GHSA-CC97-G92W-JM65

TYPO3 CMS Insecure Deserialization & Arbitrary Code Execution

Overview

Published
30 May 2024
Modified
30 May 2024
Critical GitHub advisory
1 Registry packages
0 OS packages
0 Linux distributions
Yes Fix available

Description

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.

Source: OX vulnerability database

Severity

9.8 · CRITICAL

CVSS 3.1 base score, scored by GitHub.

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

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

Affected packages · 1

Packages affected by GHSA-CC97-G92W-JM65
EcosystemPackageVulnerableFixed in
Composer (PHP) typo3/cms-core >=8.0.0, <8.7.17>=9.0.0, <9.3.2>=7.0.0, <7.6.30 8.7.179.3.27.6.30

Open a package to see all its vulnerabilities.

Operating systems

No Linux distribution reports this ID.

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.