GHSA-657m-v5vm-f6rw BIT-typo3-2021-41113 CVE-2021-41113
Cross-Site-Request-Forgery in Backend
- Severity
- 8.8 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 0.64%
- Chance of exploitation in the next 30 days. Higher than 50.67% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-309 Use of Password System for Primary Authentication
- CWE-352 Cross-Site Request Forgery (CSRF)
- Fix
- Available
- 2 packages have a fixed version
Description
Meta
- CVSS:
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C(8.2)
Problem
It has been discovered that the new TYPO3 v11 feature that allows users to create and share deep links in the backend user interface is vulnerable to cross-site-request-forgery.
The impact is the same as described in TYPO3-CORE-SA-2020-006 (CVE-2020-11069). However, it is not limited to the same site context and does not require the attacker to be authenticated. In a worst case scenario, the attacker could create a new admin user account to compromise the system.
To successfully carry out an attack, an attacker must trick his victim to access a compromised system. The victim must have an active session in the TYPO3 backend at that time.
The following Same-Site cookie settings in $GLOBALS[TYPO3_CONF_VARS][BE][cookieSameSite] are required for an attack to be successful:
- SameSite=strict: malicious evil.example.org invoking TYPO3 application at good.example.org
- SameSite=lax or none: malicious evil.com invoking TYPO3 application at example.org
Solution
Update your instance to TYPO3 version 11.5.0 which addresses the problem described.
Credits
Thanks to Richie Lee who reported this issue and to TYPO3 core & security team members Benni Mack and Oliver Hader who fixed the issue.
References
- TYPO3-CORE-SA-2021-014
- CVE-2020-11069 reintroduced in TYPO3 v11.2.0
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| typo3/cms | >= 11.2.0, < 11.5.0 |
11.5.0 |
| typo3/cms-core | >= 11.2.0, < 11.5.0 |
11.5.0 |
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 → 11.5.0
- composer
composer require typo3/cms:^11.5.0
typo3/cms-core Packagist → 11.5.0
- composer
composer require typo3/cms-core:^11.5.0
Severity breakdown
CVSS 3.1 8.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Weakness
CWE-309: Use of Password System for Primary Authentication
The use of password systems as the primary means of authentication may be subject to several flaws or shortcomings, each reducing the effectiveness of the mechanism.
How to prevent it
- Architecture and Design: In order to protect password systems from compromise, the following should be noted: Passwords should be stored safely to prevent insider attack and to ensure that -- if a system is compromised -- the passwords are not retrievable. Due to password reuse, this information may be useful in the compromise of other systems these users work with. In order to protect these passwords, they should be stored encrypted, in a non-reversible state, such that the original text password cannot be extracted from the stored value. Password aging should be strictly enforced to ensure that passwords do not remain unchanged for long periods of time. The longer a password remains in use, the higher the probability that it has been compromised. For this reason, passwords should require refreshing periodically, and users should be informed of the risk of passwords which remain in use for too long. Password strength should be enforced intelligently. Rather than restrict passwords to specific content, or specific length, users should be encouraged to use upper and lower case letters, numbers, and symbols in their passwords. The system should also ensure that no passwords are derived from dictionary words.
- Architecture and Design: Use a zero-knowledge password protocol, such as SRP.
- Architecture and Design: Ensure that passwords are stored safely and are not reversible.
- Architecture and Design: Implement password aging functionality that requires passwords be changed after a certain point.
- Architecture and Design: Use a mechanism for determining the strength of a password and notify the user of weak password use.
- Architecture and Design: Inform the user of why password protections are in place, how they work to protect data integrity, and why it is important to heed their warnings.
CWE-352: Cross-Site Request Forgery (CSRF)
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
How to prevent it
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. For example, use anti-CSRF packages such as the OWASP CSRFGuard. [REF-330] Another example is the ESAPI Session Management control, which includes a component for CSRF. [REF-45]
- Implementation: Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
- Architecture and Design: Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330). [REF-332]
- Architecture and Design: Identify especially dangerous operations. When the user performs a dangerous operation, send a separate confirmation request to ensure that the user intended to perform that operation.
- Architecture and Design: Use the "double-submitted cookie" method as described by Felten and Zeller: When a user visits a site, the site should generate a pseudorandom value and set it as a cookie on the user's machine. The site should require every form submission to include this value as a form value and also as a cookie value. When a POST request is sent to the site, the request should only be considered valid if the form value and the cookie value are the same. Because of the same-origin policy, an attacker cannot read or modify the value stored in the cookie. To successfully submit a form on behalf of the user, the attacker would have to correctly guess the pseudorandom value. If the pseudorandom value is cryptographically strong, this will be prohibitively difficult. This technique requires Javascript, so it may not work for browsers that have Javascript disabled. [REF-331]
- Architecture and Design: Do not use the GET method for any request that triggers a state change.
- Implementation: Check the HTTP Referer header to see if the request originated from an expected page. This could break legitimate functionality, because users or proxies may have disabled sending the Referer for privacy reasons.
References
Advisories
Packages
Other links
- github.com/TYPO3/typo3/security/advisories/GHSA-657m-v5vm-f6rw
- github.com/TYPO3/typo3/commit/fa51999203c5e5d913ecae5ea843ccb2b95fa33f
- github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2021…
- github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/CVE-2021-4111…
- typo3.org/security/advisory/typo3-core-sa-2020-006
- typo3.org/security/advisory/typo3-core-sa-2021-014
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