cve.bz

CVE-2022-23500 typo3 typo3: Uncontrolled Recursion

7.5 highEPSS 0.7%Fix available

High (7.5) in typo3 typo3. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in typo3/cms-core 10.4.33, 11.5.20, 9.5.38.

On this page
TYPO3 is an open source PHP based web content management system. In versions prior to 9.5.38, 10.4.33, 11.5.20, and 12.1.1, requesting invalid or non-existing resources via HTTP triggers the page error handler, which again could retrieve content to be shown as an error message from another page. This leads to a scenario in which the application is calling itself recursively - amplifying the impact of the initial attack until the limits of the web server are exceeded. This vulnerability is very similar, but not identical, to the one described in CVE-2021-21359. This issue is patched in versions 9.5.38 ELTS, 10.4.33, 11.5.20 or 12.1.1.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 56th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-04-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-674 Uncontrolled Recursion
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

  • typo3/cms-core (Packagist): fixed in 9.5.38, 10.4.33, 11.5.20
  • typo3/cms (Packagist): fixed in 10.4.33, 11.5.20

Ask an AI about this CVE

Show the promptExplain CVE-2022-23500 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-23500?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-23500?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-23500 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
typo3:typo3from 9.0.0 before 9.5.38
typo3:typo3from 10.0.0 before 10.4.33
typo3:typo3from 11.0.0 before 11.5.20

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-8c28-5mp7-v24hPackagisttypo3/cms-core>=9.0.0 <9.5.389.5.38
GHSA-8c28-5mp7-v24hPackagisttypo3/cms-core>=10.0.0 <10.4.3310.4.33
GHSA-8c28-5mp7-v24hPackagisttypo3/cms-core>=11.0.0 <11.5.2011.5.20
GHSA-8c28-5mp7-v24hPackagisttypo3/cms>=10.0.0 <10.4.3310.4.33
GHSA-8c28-5mp7-v24hPackagisttypo3/cms>=11.0.0 <11.5.2011.5.20

Attack patterns (CAPEC)

  • CAPEC-230 Serialized Data with Nested Payloads Likelihood: Medium · Severity: High
  • CAPEC-231 Oversized Serialized Data Payloads Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON