CVE-2024-55945: TYPO3 DB Check Module Vulnerable to Cross-Site Request Forgery
Summary
CVE-2024-55945: TYPO3 DB Check Module vulnerable to Cross-Site Request Forgery. Affects typo3/cms-lowlevel versions >= 11.0.0, < 11.5.42. Fixed in 11.5.42. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
TYPO3 is an open-source content management system (CMS) that enables users to create and manage websites efficiently. It is widely used for its flexibility and extensibility, allowing developers to build custom functionalities. The DB Check Module is a component within TYPO3 that helps maintain database integrity. However, this module has been found to be vulnerable to Cross-Site Request Forgery (CSRF), which can lead to unauthorized actions being performed on behalf of authenticated users.
Vulnerability Detail
The vulnerability arises from the backend user interface's handling of deep links, which are susceptible to CSRF attacks. Attackers can exploit this vulnerability by tricking users into clicking malicious links while they are logged into the TYPO3 backend. If the user interacts with a compromised link, unauthorized actions can be executed, potentially leading to data manipulation. This vulnerability is exacerbated when certain security settings are misconfigured, such as disabling the 'security.backend.enforceReferrer' feature and setting 'BE/cookieSameSite' to 'lax' or 'none'.
How To Fix
Minimum fixed version
11.5.42
This is the first release that contains the fix.
composer require typo3/cms-lowlevel:11.5.42Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, ensure that the 'security.backend.enforceReferrer' feature is enabled and configure 'BE/cookieSameSite' to 'strict' to mitigate the risk of CSRF attacks until the update can be applied.
Conclusion
The vulnerability identified as CVE-2024-55945 in the TYPO3 DB Check Module poses a significant risk due to its susceptibility to CSRF attacks. It is crucial for users to update to the latest version to mitigate this risk and ensure the integrity of their applications. Implementing the recommended workarounds can provide temporary relief until the update is applied.
See every vulnerability recorded for typo3/cms-lowlevel →
FAQ
CSRF is a type of attack that tricks the victim into submitting a malicious request, leveraging their authenticated session to perform unintended actions.
You can check your TYPO3 version against the affected range (<= 11.5.41) and update to the patched version (11.5.42 ELTS or later).
Successful exploitation can lead to unauthorized data manipulation and actions being performed in the backend, compromising the integrity of the application.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your composer.lock file. You can check if your application is affected by visiting the Vulert playground.
If an immediate update is not possible, implement the suggested workaround by adjusting the security settings to reduce the risk of CSRF attacks.
