Description
FrontAccounting through 2.4.20 stores and verifies user passwords as unsalted MD5 digests. admin/users.php passes md5($_POST['password']) to add_user() and update_user_password(), admin/change_current_user_password.php does the same when a user changes their own password, the forgotten-password path in includes/current_user.inc hashes the newly generated password the same way, and authentication calls get_user_auth($loginname, md5($password)). The codebase applies no per-password salt and contains no call to password_hash(), password_verify() or any other adaptive hash, so identical passwords yield identical digests and an attacker who obtains the user table can recover plaintext passwords with precomputed lookup tables or high-rate GPU cracking.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| FrontAccounting | FrontAccounting | ≤ 2.4.20 | — |
References
- geo-chen/oss: FrontAccounting Finding 2 third-party-advisory
- https://github.com/FrontAccountingERP/FA product
- https://github.com/FrontAccountingERP/FA/blob/9464a3ffef03c139d9396e697bce9a0a9f131a72/includes/current_user.inc#L79 technical-description
- VulnCheck Advisory: FrontAccounting through 2.4.20 Use of Unsalted MD5 for Password Storage third-party-advisory