TYPO3 Denial of Service in Frontend Record Registration

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

TYPO3’s built-in record registration functionality (aka “basic shopping cart”) using recs URL parameters is vulnerable to denial of service. Failing to properly ensure that anonymous user sessions are valid, attackers can use this vulnerability in order to create an arbitrary amount of individual session-data records in the database.

Patch / fix

fixed in 1 links 1

packagist typo3/cms-core 7.6.32, 8.7.21

github.com/TYPO3-CMS/core@5a44f93 commit

Is GHSA-hjx5-v9xg-7h25 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:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem	package	affected	fixed in
packagist	typo3/cms-core	>=8.0.0, <8.7.21 >=7.0.0, <7.6.32	8.7.21 7.6.32

Classification

Weakness

CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

GitHub Advisory GHSA-hjx5-v9xg-7h25

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.