HighGHSA-c5mj-39cf-3pp5

TYPO3 Security Misconfiguration for Backend User Accounts

Published 7 Jun 2024 · Updated 4 Dec 2024

Affected packages

typo3/cmsComposer
Affected
>=8.0.0 <8.7.23
Fixed in
8.7.23
Update to the fixed version for your release line, for example:composer require typo3/cms:^8.7.23
typo3/cmsComposer
Affected
>=9.0.0 <9.5.4
Fixed in
9.5.4
Update to the fixed version for your release line, for example:composer require typo3/cms:^9.5.4

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.

Is GHSA-c5mj-39cf-3pp5 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected typo3/cms, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.