GHSA-c5mj-39cf-3pp5
Suggest an improvement- Source
- https://github.com/advisories/GHSA-c5mj-39cf-3pp5
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/06/GHSA-c5mj-39cf-3pp5/GHSA-c5mj-39cf-3pp5.json
- JSON Data
- https://api.osv.dev/v1/vulns/GHSA-c5mj-39cf-3pp5
- Published
- 2024-06-07T17:19:38Z
- Modified
- 2024-12-04T05:37:52.473579Z
- Severity
-
- 7.3 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N CVSS Calculator
- 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.
- Database specific
{ "nvd_published_at": null, "cwe_ids": [ "CWE-287" ], "severity": "HIGH", "github_reviewed": true, "github_reviewed_at": "2024-06-07T17:19:38Z" }- 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://github.com/TYPO3/typo3
- https://typo3.org/security/advisory/typo3-core-sa-2019-002