Advisory

GHSA-c5mj-39cf-3pp5

Also known as: None

Summary

TYPO3 Security Misconfiguration for Backend User Accounts

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2024-06-07 17:19 UTC
Modified
2024-12-04 05:37 UTC

Affected packages and fixes

typo3/cms

Packagist · All systems

Affected

  • introduced 8.0.0, fixed 8.7.23 (ecosystem)

Fixed versions

8.7.23

Fix

The export has no generic command for this ecosystem.

typo3/cms

Packagist · All systems

Affected

  • introduced 9.0.0, fixed 9.5.4 (ecosystem)

Fixed versions

9.5.4

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences