| Package | Affected versions | Patched versions |
|---|---|---|
| mantisbt/mantisbt | < 2.27.2 | 2.27.2 |
| mantisbt | < 2.27.2 | 2.27.2 |
Due to an incorrect use of loose (==) instead of strict (===) comparison in the authentication code, PHP type juggling will cause interpretation of certain MD5 hashes as numbers, specifically those matching scientific notation.
On MantisBT instances configured to use the MD5 login method, user accounts having a password hash evaluating to zero (i.e. matching regex ^0+[Ee][0-9]+$) are vulnerable, allowing an attacker knowing the victim's username to login without knowledge of their actual password, using any other password having a hash evaluating to zero, for example comito5 (0e579603064547166083907005281618).
No password bruteforcing for individual users is needed, thus $g_max_failed_login_count does not protect against the attack.
Check the database for vulnerable accounts, and change those users' passwords, e.g. for MySQL:
SELECT username, email FROM mantis_user_table WHERE password REGEXP '^0+[Ee][0-9]+$'
Thanks to Harry Sintonen / Reversec for discovering and reporting the issue.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free