# CVE-2021-21339: Cleartext storage of session identifier > TYPO3 stores session identifiers in cleartext, allowing attackers to steal sessions if combined with other vulnerabilities like SQL injection. - **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 23 Mar 2021 - **Updated:** 3 Aug 2024 - **Also known as:** BIT-typo3-2021-21339, GHSA-qx3w-4864-94ch ## What is CVE-2021-21339? CVE-2021-21339 is a medium-severity vulnerability in Typo3 Typo3, published on 23 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description TYPO3 is an open source PHP based web content management system. In TYPO3 before versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 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. This is fixed in versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1. Weakness: CWE-312 (Cleartext Storage of Sensitive Information) ## Which versions are affected by CVE-2021-21339? 19 open source packages ship an affected version, including typo3/cms-core, typo3 and typo3/cms. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `typo3/cms-core` | Packagist | From 10.0.0 | 10.4.14 | | `typo3/cms-core` | Packagist | From 10.0.0 | 10.4.14 | | `typo3/cms-core` | Packagist | From 11.0.0 | 11.1.1 | | `typo3/cms-core` | Packagist | From 11.0.0 | 11.1.1 | | `typo3/cms-core` | Packagist | From 6.2.0 | 6.2.57 | | `typo3/cms-core` | Packagist | From 6.2.0 | 6.2.57 | | `typo3/cms-core` | Packagist | From 7.0.0 | 7.6.51 | | `typo3/cms-core` | Packagist | From 7.0.0 | 7.6.51 | | `typo3/cms-core` | Packagist | From 8.0.0 | 8.7.40 | | `typo3/cms-core` | Packagist | From 8.0.0 | 8.7.40 | | `typo3/cms-core` | Packagist | From 9.0.0 | 9.5.25 | | `typo3/cms-core` | Packagist | From 9.0.0 | 9.5.25 | | `typo3` | Bitnami | From 6.2.0 | 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 | | `typo3/cms` | Packagist | From 10.0.0 | 10.4.14 | | `typo3/cms` | Packagist | From 10.0.0 | 10.4.14 | | `typo3/cms` | Packagist | From 11.0.0 | 11.1.1 | | `typo3/cms` | Packagist | From 11.0.0 | 11.1.1 | | `typo3/cms` | Packagist | From 9.0.0 | 9.5.25 | | `typo3/cms` | Packagist | From 9.0.0 | 9.5.25 | Products: Typo3 Typo3. ## How do I fix CVE-2021-21339? Upgrade typo3/cms-core to a fixed version for your release line: 10.4.14, 11.1.1, 6.2.57 or 7.6.51. ## Is CVE-2021-21339 being exploited? There is no known exploitation of CVE-2021-21339 in the wild and no public exploit code. ## Other vulnerabilities in Typo3 Typo3 - [CVE-2009-0258](https://insights.sbomify.com/CVE-2009-0258/): Indexed Search Engine for TYPO3 Command Execution via Metacharacter Injection (critical 10.0) - [CVE-2011-3583](https://insights.sbomify.com/CVE-2011-3583/): Typo3 SQL injection due to faulty prepared statements (critical 9.8) - [CVE-2011-4628](https://insights.sbomify.com/CVE-2011-4628/): Typo3 Authentication Bypass (critical 9.8) - [CVE-2023-24814](https://insights.sbomify.com/CVE-2023-24814/): Persisted Cross-Site Scripting in Frontend Rendering in typo3 (high 8.8) - [CVE-2021-41113](https://insights.sbomify.com/CVE-2021-41113/): Cross-Site-Request-Forgery in Backend URI Handling in Typo3 (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2021-21339 and fix it if it is affected. What it is: CVE-2021-21339 is a medium-severity vulnerability in Typo3 Typo3, published on 23 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2021-21339 in the wild and no public exploit code. Affected packages and fixed versions: - typo3/cms-core (Packagist): affected from 10.0.0; fixed in 10.4.14 - typo3/cms-core (Packagist): affected from 10.0.0; fixed in 10.4.14 - typo3/cms-core (Packagist): affected from 11.0.0; fixed in 11.1.1 - typo3/cms-core (Packagist): affected from 11.0.0; fixed in 11.1.1 - typo3/cms-core (Packagist): affected from 6.2.0; fixed in 6.2.57 - typo3/cms-core (Packagist): affected from 6.2.0; fixed in 6.2.57 - typo3/cms-core (Packagist): affected from 7.0.0; fixed in 7.6.51 - typo3/cms-core (Packagist): affected from 7.0.0; fixed in 7.6.51 - typo3/cms-core (Packagist): affected from 8.0.0; fixed in 8.7.40 - typo3/cms-core (Packagist): affected from 8.0.0; fixed in 8.7.40 - typo3/cms-core (Packagist): affected from 9.0.0; fixed in 9.5.25 - typo3/cms-core (Packagist): affected from 9.0.0; fixed in 9.5.25 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2021-21339/ (Markdown: https://insights.sbomify.com/CVE-2021-21339/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2021-21339 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-21339 - OSV: https://osv.dev/vulnerability/CVE-2021-21339 --- From sbomify Insights: https://insights.sbomify.com/CVE-2021-21339/ Summaries are generated and may contain mistakes; the official description above is the record.