Skip to content

TYPO3 vulnerable to Weak Authentication in Session Handling

Moderate severity GitHub Reviewed Published Nov 14, 2023 in TYPO3/typo3 • Updated Dec 15, 2023

Package

composer typo3/cms-core (Composer)

Affected versions

>= 8.0.0, <= 8.7.54
>= 9.0.0, <= 9.5.43
>= 10.0.0, <= 10.4.40
>= 11.0.0, <= 11.5.32
>= 12.0.0, <= 12.4.7

Patched versions

8.7.55
9.5.44
10.4.41
11.5.33
12.4.8

Description

CVSS: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N/E:X/RL:O/RC:C (4.0)

Problem

Given that there are at least two different sites in the same TYPO3 installation - for instance first.example.org and second.example.com - then a session cookie generated for the first site can be reused on the second site without requiring additional authentication.

This vulnerability primarily affects the frontend of the website. It's important to note that exploiting this vulnerability requires a valid user account.

Solution

Update to TYPO3 versions 8.7.55 ELTS, 9.5.44 ELTS, 10.4.41 ELTS, 11.5.33, 12.4.8 that fix the problem described above.

Credits

Thanks to Rémy Daniel who reported this issue, and to TYPO3 core & security team member Benjamin Franzke who fixed the issue.

References

References

@ohader ohader published to TYPO3/typo3 Nov 14, 2023
Published to the GitHub Advisory Database Nov 14, 2023
Reviewed Nov 14, 2023
Published by the National Vulnerability Database Nov 14, 2023
Last updated Dec 15, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

EPSS score

0.056%
(24th percentile)

Weaknesses

CVE ID

CVE-2023-47127

GHSA ID

GHSA-3vmm-7h4j-69rm

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.