In “Dolibarr” application, v3.3.beta1_20121221 to v13.0.2 have “Modify” access for admin level users to change other user’s details but fails to validate already existing “Login” name, while renaming the user “Login”. This leads to complete account takeover of the victim user. This happens since the password gets overwritten for the victim user having a similar login name.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Dolibarr | Dolibarr | 3.3.1 (including) | 13.0.2 (including) |
| Dolibarr_erp/crm | Dolibarr | 3.3.0-beta1 (including) | 3.3.0-beta1 (including) |
| Dolibarr_erp/crm | Dolibarr | 3.3.0-beta2 (including) | 3.3.0-beta2 (including) |
| Dolibarr | Ubuntu | esm-apps/xenial | * |
| Dolibarr | Ubuntu | trusty | * |
| Dolibarr | Ubuntu | xenial | * |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: