- Release Date: October 30, 2019
- Component Type: LDAP passwort storage & authentication (via my.typo3.org)
- Impact: Truncated password during authentication
- Serverity: critical
- Suggested CVSS v3: AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:L/E:F/RL:O/RC:C
- CWE: CWE-327
Passwords of users on my.typo3.org - the management hub that is used to authenticate against multiple other typo3.org related services and tools - were stored using a broken cryptographic algorithm. Traditional CRYPT-DES has been used to generate a cryptographic hash of the plaintext password - due to the limitation on traditional DES, only the first eight characters of the password were used.
As a result, the first eight characters were sufficient to log in at my.typo3.org - even if the initial password was much longer. In case this sequence would have contained weak or guessable phrases - the potential of dictionary-based attacks was much higher to be successful. For instance, "password" would have been enough even if the actual plaintext password was "password%faH3!ieXees.h1iK".
In total three different hashing algorithms CRYPT-DES, MD5 and SHA1 had been applied and stored.
The following platforms were affected:
- typo3.com (partner network)
Broken CRYPT-DES algorithm has been disabled and corresponding hashes removed from LDAP password storage. All the above systems have now been converted to state of the art password hashing algorithm CRYPT-SHA-512 and a minimum password length of 12 characters, see https://git-t3o.typo3.org/t3o/my/commit/366392b103f40095c3df4076a0fa90c383cedcfd for implementation details.
Audits controls done by the maintainers of the platforms mentioned above have shown, that we have no reason to believe that this vulnerability has been unlawfully exploited.
As a precaution, we ask you to change your TYPO3.org password.
- login at https://my.typo3.org/
- change password at https://my.typo3.org/my-profile/change-password
As an alternative, you can reset your password via the forgot password option.
Thanks to TYPO3 framework merger Frank Nägler who reported this issue.
Users having a TYPO3.org account have been informed already on October 28, 2019, on behalf of the TYPO3 Association. This public service announcement published by the TYPO3 security team aims to respond to questions we received to provide more technical insights into the original vulnerability and how it has been addressed in a collaborative effort among involved TYPO3 teams.