GHSA-3vmm-7h4j-69rm BIT-typo3-2023-47127 CVE-2023-47127
TYPO3 vulnerable to Weak Authentication in Session Handling
- Severity
- 4.2 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.56%
- Chance of exploitation in the next 30 days. Higher than 46.68% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Fix
8.7.55- Upgrade typo3/cms-core to this version or later
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
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| typo3/cms-core | >= 8.0.0, < 8.7.55 |
8.7.55 |
| typo3/cms-core | >= 9.0.0, < 9.5.44 |
9.5.44 |
| typo3/cms-core | >= 10.0.0, < 10.4.41 |
10.4.41 |
| typo3/cms-core | >= 11.0.0, < 11.5.33 |
11.5.33 |
| typo3/cms-core | >= 12.0.0, < 12.4.8 |
12.4.8 |
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-core Packagist → 8.7.55
- composer
composer require typo3/cms-core:^8.7.55
Severity breakdown
CVSS 3.1 4.2
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
Weakness
CWE-287: Improper Authentication
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
How to prevent it
- Architecture and Design: Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
CWE-302: Authentication Bypass by Assumed-Immutable Data
The authentication scheme or implementation uses key data elements that are assumed to be immutable, but can be controlled or modified by the attacker.
How to prevent it
- Architecture and Design, Operation, Implementation: Implement proper protection for immutable data (e.g. environment variable, hidden form fields, etc.)
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why 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 |
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