Skip to content

GHSA-qx3w-4864-94ch BIT-typo3-2021-21339 CVE-2021-21339

Cleartext storage of session identifier

Medium Packagist
Severity
5.9 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.92%
Chance of exploitation in the next 30 days. Higher than 60.23% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-312 Cleartext Storage of Sensitive Information
Fix
Available
2 packages have a fixed version

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

Affected versions

Packagist

PackageVulnerableFixed in
typo3/cms
>= 10.0.0, < 10.4.14
10.4.14
typo3/cms
>= 11.0.0, < 11.1.1
11.1.1
typo3/cms
>= 9.0.0, < 9.5.25
9.5.25
typo3/cms-core
>= 6.2.0, < 6.2.57
6.2.57
typo3/cms-core
>= 7.0.0, < 7.6.51
7.6.51
typo3/cms-core
>= 8.0.0, < 8.7.40
8.7.40
typo3/cms-core
>= 10.0.0, < 10.4.14
10.4.14
typo3/cms-core
>= 11.0.0, < 11.1.1
11.1.1
typo3/cms-core
>= 9.0.0, < 9.5.25
9.5.25

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

typo3/cms Packagist → 10.4.14

composer
composer require typo3/cms:^10.4.14

typo3/cms-core Packagist → 6.2.57

composer
composer require typo3/cms-core:^6.2.57

Severity breakdown

CVSS 3.1 5.9

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

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

Weakness

CWE-312: Cleartext Storage of Sensitive Information

The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.

How to prevent it
  • Implementation, System Configuration, Operation: When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to encrypt the data at rest. [REF-1297] [REF-1299] [REF-1301]
  • Implementation, System Configuration, Operation: In some systems/environments such as cloud, the use of "double encryption" (at both the software and hardware layer) might be required, and the developer might be solely responsible for both layers, instead of shared responsibility with the administrator of the broader system/environment.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-68jx-f42c-7599
TYPO3 CMS - Broken Access Control in Backend and Install Tool
High Also affects typo3/cms-core
GHSA-chm7-4vch-h8vr
TYPO3 CMS has Broken Access Control in its Media Module
High Also affects typo3/cms-core
GHSA-jh32-v29g-68pq
TYPO3 CMS has Privilege Escalation & SQL Injection in its Form Framework
High Also affects typo3/cms-core
GHSA-c78m-c52x-jgwp
TYPO3 CMS has Insecure Deserialization via Core API
Medium Also affects typo3/cms-core
GHSA-jf56-v8jc-jcc5
TYPO3 CMS has Broken Access Control in its File Abstraction Layer
Low Also affects typo3/cms-core
GHSA-2j54-93q2-3hjq
TYPO3 CMS has Broken Access Control in Backend API
Medium Also affects typo3/cms-core
GHSA-q93m-25xv-94hh
TYPO3 CMS: Broken Access Control in Media Module
Medium Also affects typo3/cms-core
GHSA-qcmw-6rm2-5x78
TYPO3 CMS has Broken Access Control in its DataHandler
Medium Also affects typo3/cms-core
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor