CVE-2010-5104: TYPO3 Sensitive Information Disclosure via escapeStrForLike method
Summary
CVE-2010-5104: TYPO3 Sensitive Information Disclosure via escapeStrForLike method. Affects typo3/cms-core across 3 version ranges.
>= 4.2.0, < 4.2.16
>= 4.3.0, < 4.3.9
>= 4.4.0, < 4.4.5
Fixed in 4.2.16, 4.3.9 or 4.4.5, depending on the release line you run. 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) written in PHP. It is widely used for building websites and web applications. The TYPO3 CMS Core package is responsible for the core functionality of TYPO3. It provides features such as content management, user management, and database connectivity. This vulnerability affects TYPO3 versions 4.2.x, 4.3.x, and 4.4.x.
Vulnerability Detail
The escapeStrForLike method in TYPO3 4.2.x before 4.2.16, 4.3.x before 4.3.9, and 4.4.x before 4.4.5 does not properly escape input when the MySQL database is set to sql_mode NO_BACKSLASH_ESCAPES. This allows remote attackers to obtain sensitive information by using wildcard characters in a LIKE query. An attacker can exploit this vulnerability to retrieve sensitive data from the database, potentially compromising the confidentiality of user information or other sensitive data stored in the TYPO3 CMS.
How To Fix
Fixed versions by release line
The minimum fixed version depends on the release line you run.
-
>= 4.2.0, < 4.2.164.2.16composer require typo3/cms-core:4.2.16 -
>= 4.3.0, < 4.3.94.3.9composer require typo3/cms-core:4.3.9 -
>= 4.4.0, < 4.4.54.4.5composer require typo3/cms-core:4.4.5
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
If upgrading to a fixed version is not immediately possible, a workaround can be implemented by modifying the MySQL database configuration. By setting the sql_mode to a value that includes BACKSLASH_ESCAPES, the vulnerability can be mitigated. However, this workaround may have implications on other parts of the application that rely on the NO_BACKSLASH_ESCAPES mode. It is recommended to thoroughly test the application after applying this workaround.
Conclusion
The TYPO3 CMS Core package is vulnerable to a sensitive information disclosure vulnerability. Upgrading to the fixed versions or applying the provided workaround is crucial to mitigate the risk of data exposure. It is recommended to follow the recommended steps and test the application thoroughly after applying any changes. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for typo3/cms-core →
FAQ
TYPO3 is an open-source content management system (CMS) written in PHP. It is widely used for building websites and web applications.
This vulnerability affects TYPO3 versions 4.2.x, 4.3.x, and 4.4.x.
An attacker can exploit this vulnerability by using wildcard characters in a LIKE query to retrieve sensitive information from the database.
The vulnerability can lead to the disclosure of sensitive information stored in the TYPO3 CMS, potentially compromising the confidentiality of user data or other sensitive data.
Yes, a workaround is available by modifying the MySQL database configuration. However, it is recommended to upgrade to a fixed version as soon as possible.
References
Related vulnerabilities
Recent vulnerabilities recorded for typo3/cms-core.
