GHSA-hh95-5xm5-v8v7: Typo3/cms TYPO3 CMS Possible Insecure Deserialization Vulnerability

HIGH
Share
CVSS 8.1
Published
Advisory Summary

GHSA-hh95-5xm5-v8v7 is a HIGH (CVSS 8.1) typo3 cms possible insecure deserialization vulnerability (General Security Weakness) affecting Typo3/cms libraries in the Packagist ecosystem. The issue involves typo3 cms possible insecure deserialization in extbase request handling. Remediation is available by upgrading affected packages to version 8.7.30, 9.5.12.

GHSA-hh95-5xm5-v8v7 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-hh95-5xm5-v8v7
Severity HIGH
CVSS v3.1 Base Score 8.1
CWE Classification General Security Weakness
Affected Product Typo3/cms
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 8.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix GHSA-hh95-5xm5-v8v7

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: 8.7.30 
Upgrade typo3/cms to 8.7.30
typo3/cms fixed: 9.5.12 
Upgrade typo3/cms to 9.5.12
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-hh95-5xm5-v8v7, 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 8.7.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 General Security Weakness. 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

It has been discovered that request handling in Extbase can be vulnerable to insecure deserialization. User submitted payload has to be signed with a corresponding HMAC-SHA1 using the sensitive TYPO3 encryptionKey as secret - invalid or unsigned payload is not deserialized. However, since sensitive information could have been leaked by accident (e.g. in repositories or in commonly known and unprotected backup files), there is the possibility that attackers know the private encryptionKey and are able to calculate the required HMAC-SHA1 to allow a malicious payload to be deserialized. Requirements for successfully exploiting this vulnerability (all of the following): - rendering at least one Extbase plugin in the frontend - encryptionKey has been leaked (from LocalConfiguration.php or corresponding .env file)

GHSA-hh95-5xm5-v8v7 Affected Typo3/cms Versions

2 component(s)
Fixed Versions:
8.7.309.5.12
Product / Package Ecosystem Affected Versions Fixed Version
typo3/cms
 Packagist
≥ 8.0.0
< 8.7.30
8.7.30
typo3/cms
 Packagist
≥ 9.0.0
< 9.5.12
9.5.12

References

Security Fix Commit FIX COMMIT
https://github.com/TYPO3/typo3/commit/57e4ed35a6e58521a931855e702b2688b3bc3d62
Security Fix Commit FIX COMMIT
https://github.com/TYPO3/typo3/commit/b1626ad8fd4aebedc15e424a76f86094d78b2564
Typo3/cms Source Repository REPOSITORY
https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/2019-12-17-7.yaml
Typo3/cms Source Repository REPOSITORY
https://github.com/TYPO3/typo3
Typo3/cms Security Information SECURITY
https://typo3.org/security/advisory/typo3-psa-2019-011

Frequently Asked Questions

What is GHSA-hh95-5xm5-v8v7?
GHSA-hh95-5xm5-v8v7 is a security vulnerability in Typo3/cms involving TYPO3 CMS Possible Insecure Deserialization in Extbase Request Handling under General Security Weakness.
Which Typo3/cms versions are affected?
Affected versions include releases prior to 8.7.30, 9.5.12 across affected packages: typo3/cms.
What version fixes GHSA-hh95-5xm5-v8v7?
Upgrading to 8.7.30, 9.5.12 (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 8.7.30, 9.5.12. Upgrade your dependency to 8.7.30, 9.5.12 or later.
What is the CVSS score of GHSA-hh95-5xm5-v8v7?
GHSA-hh95-5xm5-v8v7 has a CVSS v3.1 base score of 8.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with GHSA-hh95-5xm5-v8v7?
GHSA-hh95-5xm5-v8v7 is classified under General Security Weakness.
How can I check Packagist dependencies for GHSA-hh95-5xm5-v8v7?
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-hh95-5xm5-v8v7",
  "modified" : "2024-06-07T17:07:03Z",
  "published" : "2024-06-07T17:07:03Z",
  "aliases" : [ ],
  "summary" : "TYPO3 CMS Possible Insecure Deserialization in Extbase Request Handling",
  "details" : "It has been discovered that request handling in Extbase can be vulnerable to insecure deserialization. User submitted payload has to be signed with a corresponding HMAC-SHA1 using the sensitive TYPO3 encryptionKey as secret - invalid or unsigned payload is not deserialized.\n\nHowever, since sensitive information could have been leaked by accident (e.g. in repositories or in commonly known and unprotected backup files), there is the possibility that attackers know the private encryptionKey and are able to calculate the required HMAC-SHA1 to allow a malicious payload to be deserialized.\n\nRequirements for successfully exploiting this vulnerability (all of the following):\n\n- rendering at least one Extbase plugin in the frontend\n- encryptionKey has been leaked (from LocalConfiguration.php or corresponding .env file)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/cms"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "8.0.0"
      }, {
        "fixed" : "8.7.30"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/cms"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "9.0.0"
      }, {
        "fixed" : "9.5.12"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/TYPO3/typo3/commit/57e4ed35a6e58521a931855e702b2688b3bc3d62"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/TYPO3/typo3/commit/b1626ad8fd4aebedc15e424a76f86094d78b2564"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/2019-12-17-7.yaml"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/TYPO3/typo3"
  }, {
    "type" : "WEB",
    "url" : "https://typo3.org/security/advisory/typo3-psa-2019-011"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-06-07T17:07:03Z",
    "nvd_published_at" : null
  }
}