GHSA-ppgf-8745-8pgx: Typo3/cms Insecure Deserialization & Arbitrary Code Vulnerability

HIGH
Share
CWE-502
Published
Advisory Summary

GHSA-ppgf-8745-8pgx is a HIGH insecure deserialization & arbitrary code vulnerability (CWE-502: Deserialization of Untrusted Data) affecting Typo3/cms libraries in the Packagist ecosystem. The issue involves insecure deserialization & arbitrary code execution in typo3 cms. Remediation is available by upgrading affected packages to version 7.6.30, 8.7.17, 9.3.2.

GHSA-ppgf-8745-8pgx at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-ppgf-8745-8pgx
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-502: Deserialization of Untrusted Data
Affected Product Typo3/cms
Package Ecosystem Packagist
Published Date
Last Updated

How to Fix GHSA-ppgf-8745-8pgx

To remediate this vulnerability, upgrade all affected Typo3/cms dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

typo3/cms fixed: 7.6.30 
Upgrade typo3/cms to 7.6.30
typo3/cms fixed: 8.7.17 
Upgrade typo3/cms to 8.7.17
typo3/cms fixed: 9.3.2 
Upgrade typo3/cms to 9.3.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for typo3/cms

How to Check if You Are Affected

To determine whether your application is affected by GHSA-ppgf-8745-8pgx, inspect your project dependencies for Typo3/cms:

inspect dependencies for typo3/cms

Analyze the terminal output to locate any version of Typo3/cms in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 7.6.30), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-502: Deserialization of Untrusted Data, where the product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. In Typo3/cms, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

GHSA-ppgf-8745-8pgx Affected Typo3/cms Versions

3 component(s)
Fixed Versions:
7.6.308.7.179.3.2
Product / Package Ecosystem Affected Versions Fixed Version
typo3/cms
 Packagist
≥ 7.0.0
< 7.6.30
7.6.30
typo3/cms
 Packagist
≥ 8.0.0
< 8.7.17
8.7.17
typo3/cms
 Packagist
≥ 9.0.0
< 9.3.2
9.3.2

References

Typo3/cms Source Repository REPOSITORY
https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/2018-07-12-2.yaml
Typo3/cms Security Information SECURITY
https://typo3.org/security/advisory/typo3-core-sa-2018-002

Frequently Asked Questions

What is GHSA-ppgf-8745-8pgx?
GHSA-ppgf-8745-8pgx is a security vulnerability in Typo3/cms involving Insecure Deserialization & Arbitrary Code Execution in TYPO3 CMS under CWE-502: Deserialization of Untrusted Data.
Which Typo3/cms versions are affected?
Affected versions include releases prior to 7.6.30, 8.7.17, 9.3.2 across affected packages: typo3/cms.
What version fixes GHSA-ppgf-8745-8pgx?
Upgrading to 7.6.30, 8.7.17, 9.3.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is typo3/cms affected?
Yes, typo3/cms is affected in releases prior to 7.6.30, 8.7.17, 9.3.2. Upgrade your dependency to 7.6.30, 8.7.17, 9.3.2 or later.
What CWE is associated with GHSA-ppgf-8745-8pgx?
GHSA-ppgf-8745-8pgx is classified under CWE-502: Deserialization of Untrusted Data (The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.).
How can I check Packagist dependencies for GHSA-ppgf-8745-8pgx?
Run the dependency tree command: 'inspect dependencies for typo3/cms'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-ppgf-8745-8pgx",
  "modified" : "2024-06-05T16:41:48Z",
  "published" : "2024-06-05T16:41:48Z",
  "aliases" : [ ],
  "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" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/cms"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "7.0.0"
      }, {
        "fixed" : "7.6.30"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/cms"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "8.0.0"
      }, {
        "fixed" : "8.7.17"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/cms"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "9.0.0"
      }, {
        "fixed" : "9.3.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/2018-07-12-2.yaml"
  }, {
    "type" : "WEB",
    "url" : "https://typo3.org/security/advisory/typo3-core-sa-2018-002"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-502" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-06-05T16:41:48Z",
    "nvd_published_at" : null
  }
}