Advisory

GHSA-hh95-5xm5-v8v7

Also known as: None

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.

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)

Severity

High Basis: The source's own band: HIGH

Dates

Published
2024-06-07 17:07 UTC
Modified
2024-12-04 05:40 UTC

Affected packages and fixes

typo3/cms

Packagist · All systems

Affected

  • introduced 8.0.0, fixed 8.7.30 (ecosystem)

Fixed versions

8.7.30

Fix

The export has no generic command for this ecosystem.

typo3/cms

Packagist · All systems

Affected

  • introduced 9.0.0, fixed 9.5.12 (ecosystem)

Fixed versions

9.5.12

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