FrontAccounting through 2.4.20 Use of Unsalted MD5 for Password Storage
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| FrontAccounting | FrontAccounting | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Frontaccounting | Frontaccounting |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.307% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | FrontAccounting through 2.4.20 Use of Unsalted MD5 for Password Storage | |
| First Time appeared |
Frontaccounting
Frontaccounting frontaccounting |
|
| Weaknesses | CWE-916 | |
| CPEs | cpe:2.3:a:frontaccounting:frontaccounting:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Frontaccounting
Frontaccounting frontaccounting |
|
| References |
|
|
| Metrics |
cvssV3_1
|