TYPO3 CMS Insecure Deserialization

published 2024-05-30 2y ago modified 2024-12-05 last yr.

cvss: 7.5; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

It has been discovered that the Form Framework (system extension `form`) is vulnerable to Insecure Deserialization when being used with the additional PHP PECL package `yaml`, which is capable of unserializing YAML contents to PHP objects. A valid backend user account as well as having PHP setting `yaml.decode_php` enabled is needed to exploit this vulnerability (which is the default value according to PHP documentation).

Patch / fix

fixed in 1

packagist typo3/cms-core 8.7.17, 9.3.1

Is GHSA-96jg-pmc4-cx39 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by	version	score	vector
GitHub	3.1	7.5	CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
packagist	typo3/cms-core	>=8.5.0, <8.7.17 >=9.0.0, <9.3.1	8.7.17 9.3.1

Classification

Weakness

CWE-502 Deserialization of Untrusted Data

References

Sources

GitHub Advisory GHSA-96jg-pmc4-cx39

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.