GHSA-c5mj-39cf-3pp5: TYPO3 Security Misconfiguration for Backend User Accounts
When using the TYPO3 backend in order to create new backend user accounts, database records containing insecure or empty credentials might be persisted. When the type of user account is changed - which might be entity type or the admin flag for backend users - the backend form is reloaded in order to reflect changed configuration possibilities.
Published Jun 7, 2024
Affected packages
typo3/cms
- Ecosystem
- Composer (PHP)
- Affected
- >= 8.0.0, < 8.7.23
- Fixed in
- 8.7.23
- Check
composer show typo3/cms
typo3/cms
- Ecosystem
- Composer (PHP)
- Affected
- >= 9.0.0, < 9.5.4
- Fixed in
- 9.5.4
- Check
composer show typo3/cms
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
When using the TYPO3 backend in order to create new backend user accounts, database records containing insecure or empty credentials might be persisted. When the type of user account is changed - which might be entity type or the admin flag for backend users - the backend form is reloaded in order to reflect changed configuration possibilities. However, this leads to persisting the current state as well, which can result into some of the following:
- account contains empty login credentials (username and/or password)
- account is incomplete and contains weak credentials (username and/or password)
Albeit the functionality provided by the TYPO3 core cannot be used either with empty usernames or empty passwords, it still can be a severe vulnerability to custom authentication service implementations.
This weakness cannot be directly exploited and requires interaction on purpose by some backend user having according privileges.
References
- https://github.com/TYPO3/typo3/commit/b3608d14e1915030cde272000a247cb6d5f982b8
- https://github.com/TYPO3/typo3/commit/e4d0cff40a4f8f597e52c20fff529e206bb62703
- https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/2019-01-22-2.yaml
- https://typo3.org/security/advisory/typo3-core-sa-2019-002
- https://github.com/advisories/GHSA-c5mj-39cf-3pp5
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesGHSA-2rcw-9hrm-8q7q
TYPO3 Cross-Site Scripting in Frontend User Login
medium5.4Jun 7, 2024GHSA-4h5c-5g25-v7fh
TYPO3 Cross-Site Scripting in Form Framework
medium6.1Jun 7, 2024GHSA-6487-3qvg-8px9
TYPO3 Information Disclosure in Install Tool
medium5.3Jun 7, 2024GHSA-772m-43f3-hmf8
TYPO3 Broken Access Control in Localization Handling
medium6.5Jun 7, 2024GHSA-7q33-hxwj-7p8v
TYPO3 Cross-Site Scripting in Backend Modal Component
medium5.4Jun 7, 2024GHSA-85ch-44w7-rf32
TYPO3 Cross-Site Scripting in Fluid ViewHelpers
medium6.1Jun 7, 2024
