CVE-2018-16809: Dolibarr SQL injection via the integer parameters qty and value_unit
Summary
CVE-2018-16809: Dolibarr SQL injection via the integer parameters qty and value_unit. Affects dolibarr/dolibarr versions >= 3.8, <= 7.0.0. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Dolibarr is an open-source ERP and CRM software designed for small and medium-sized businesses. It provides various modules for managing expenses, invoices, inventory, and more. The expense reports module in Dolibarr allows users to create and manage expense reports, providing features such as adding expenses, calculating totals, and generating reports. However, a vulnerability has been discovered in Dolibarr versions up to 7.0.0 that allows SQL injection through the integer parameters 'qty' and 'value_unit' in the 'expensereport/card.php' file. This vulnerability can be exploited by an attacker to execute arbitrary SQL queries, potentially leading to unauthorized access, data manipulation, or other malicious activities.
Vulnerability Detail
The vulnerability in Dolibarr arises from insufficient input validation in the 'expensereport/card.php' file. By manipulating the 'qty' and 'value_unit' parameters, an attacker can inject malicious SQL code into the underlying database query. This can result in the execution of arbitrary SQL statements, potentially compromising the confidentiality, integrity, and availability of the system. The impact of this vulnerability can range from unauthorized access to sensitive data to complete takeover of the affected system.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a temporary workaround, users can implement input validation and sanitization measures within their own code to mitigate the risk of SQL injection. This can involve validating and filtering user input to ensure it conforms to expected formats and does not contain any malicious characters or SQL statements. However, it is important to note that relying solely on input validation is not a comprehensive solution and should be accompanied by upgrading to a patched version of Dolibarr.
Conclusion
The SQL injection vulnerability in Dolibarr versions up to 7.0.0 poses a significant risk to the confidentiality, integrity, and availability of affected systems. It is crucial for users to upgrade to a patched version of Dolibarr and implement proper input validation and sanitization measures to mitigate the risk of SQL injection attacks. For further assistance and support in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for dolibarr/dolibarr →
FAQ
Dolibarr is an open-source ERP and CRM software designed for small and medium-sized businesses. It provides various modules for managing expenses, invoices, inventory, and more.
The vulnerability allows for SQL injection, which can lead to unauthorized access, data manipulation, and other malicious activities. The impact can range from exposure of sensitive data to complete system compromise.
To fix this vulnerability, it is recommended to upgrade Dolibarr to a version that includes the necessary security patches. Additionally, implementing proper input validation and sanitization measures is crucial to prevent similar vulnerabilities.
As a temporary workaround, users can implement input validation and sanitization measures within their own code. However, this should be accompanied by upgrading to a patched version of Dolibarr for comprehensive protection.
For more information about this vulnerability, you can refer to the Dolibarr project's official documentation, security advisories, or consult with security experts.
References
Related vulnerabilities
Recent vulnerabilities recorded for dolibarr/dolibarr.
