VDB
Sign up
HIGH7.3

GHSA-c5mj-39cf-3pp5

TYPO3 Security Misconfiguration for Backend User Accounts

Quick fix

GHSA-c5mj-39cf-3pp5 — typo3/cms: upgrade to the fixed version with the command below.

composer require typo3/cms:^8.7.23

Details

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.

Are you affected?

Enter the version of the package you're using.

Affected packages

Packagist/typo3/cms
Introduced in: 8.0.0Fixed in: 8.7.23
Fixcomposer require typo3/cms:^8.7.23
Packagist/typo3/cms
Introduced in: 9.0.0Fixed in: 9.5.4
Fixcomposer require typo3/cms:^9.5.4

References