Compliance Impact

The provided information does not specify how the vulnerability in Dolibarr ERP CRM affects compliance with common standards and regulations such as GDPR or HIPAA.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability allows an attacker to bypass authorization controls remotely by manipulating the ID parameter. This could lead to unauthorized access to sensitive messaging functions or data within the Dolibarr ERP CRM system.

Such unauthorized access may compromise the confidentiality of information, potentially exposing private communications or business data.

Useful 0 Not Useful 0

Mitigation Strategies

The immediate step to mitigate this vulnerability is to upgrade Dolibarr ERP CRM to version 23.0.3, which includes the patch fixing the authorization bypass issue.

This upgrade addresses the vulnerability found in versions 23.0.0, 23.0.1, and 23.0.2 by applying the patch identified by commit 119b3606c7a701747a57a1f18b1a9e7666f678e2.

Useful 0 Not Useful 0

Executive Summary

This vulnerability exists in Dolibarr ERP CRM versions 23.0.0, 23.0.1, and 23.0.2 within an unknown function in the file htdocs/user/messaging.php. It involves manipulation of the argument ID, which leads to an authorization bypass, allowing an attacker to gain unauthorized access or perform actions they should not be permitted to do. The attack can be executed remotely.

The issue is fixed by upgrading to Dolibarr version 23.0.3, which includes a patch identified by commit 119b3606c7a701747a57a1f18b1a9e7666f678e2.

Useful 0 Not Useful 0

Detection Guidance

This vulnerability involves an authorization bypass via manipulation of the argument ID in the file htdocs/user/messaging.php of Dolibarr ERP CRM versions 23.0.0, 23.0.1, and 23.0.2.

To detect this vulnerability on your system, you can check the version of Dolibarr ERP CRM installed. If it is one of the affected versions (23.0.0, 23.0.1, or 23.0.2), your system is vulnerable.

You can also attempt to detect unauthorized access attempts by monitoring HTTP requests targeting the messaging.php file with manipulated ID parameters.

• Use a command to identify the Dolibarr version, for example, by checking the application version file or metadata.
• Use network monitoring tools like tcpdump or Wireshark to capture HTTP requests to htdocs/user/messaging.php and analyze for suspicious ID parameter manipulations.
• Example command to check version in a Linux environment (adjust path as needed): cat /path/to/dolibarr/version.php | grep 'version'
• Example command to monitor HTTP requests to messaging.php: tcpdump -i any -A -s 0 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)' | grep 'messaging.php'

Upgrading to Dolibarr version 23.0.3 or later is the recommended mitigation.

Useful 0 Not Useful 0