Skip to content

Cleartext storage of session identifier

Moderate severity GitHub Reviewed Published Mar 16, 2021 in TYPO3/typo3 • Updated Feb 2, 2024

Package

composer typo3/cms (Composer)

Affected versions

>= 10.0.0, < 10.4.14
>= 11.0.0, < 11.1.1
>= 9.0.0, < 9.5.25

Patched versions

10.4.14
11.1.1
9.5.25
composer typo3/cms-core (Composer)
>= 6.2.0, <= 6.2.56
>= 7.0.0, <= 7.6.50
>= 8.0.0, <= 8.7.39
>= 10.0.0, < 10.4.14
>= 11.0.0, < 11.1.1
>= 9.0.0, < 9.5.25
6.2.57
7.6.51
8.7.40
10.4.14
11.1.1
9.5.25

Description

Problem

User session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.

Solution

Update to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.

Credits

Thanks to TYPO3 security team member Oliver Hader who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader who fixed the issue.

References

References

@ohader ohader published to TYPO3/typo3 Mar 16, 2021
Reviewed Mar 23, 2021
Published to the GitHub Advisory Database Mar 23, 2021
Published by the National Vulnerability Database Mar 23, 2021
Last updated Feb 2, 2024

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
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:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.168%
(54th percentile)

Weaknesses

CVE ID

CVE-2021-21339

GHSA ID

GHSA-qx3w-4864-94ch

Source code

No known source code

Credits

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