Skip to content

GHSA-6j62-m2vv-wc3m CVE-2018-10092

Dolibarr arbitrary commands execution

High Packagist
Severity
8.0 / 10
High · CVSS 3.0
Exploit chance (EPSS)
1.97%
Chance of exploitation in the next 30 days. Higher than 80.44% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-862 Missing Authorization
Fix
7.0.2
Upgrade dolibarr/dolibarr to this version or later

Description

The admin panel in Dolibarr before 7.0.2 might allow remote attackers to execute arbitrary commands by leveraging support for updating the antivirus command and parameters used to scan file uploads.

Affected versions

Packagist

PackageVulnerableFixed in
dolibarr/dolibarr
< 7.0.2
7.0.2

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

dolibarr/dolibarr Packagist → 7.0.2

composer
composer require dolibarr/dolibarr:^7.0.2

Severity breakdown

CVSS 3.0 8.0

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-862: Missing Authorization

The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

How to prevent it
  • Architecture and Design: Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • Architecture and Design: Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].
  • Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
  • Architecture and Design: For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page. One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
  • System Configuration, Installation: Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-v5fq-cf5m-vwv7
Dolibarr has SQL Injection in societe/class/societe.class.php via localtax1_value parameter
High Also affects dolibarr/dolibarr
GHSA-7fg5-vc77-69fp
Dolibarr ERP CRM is vulnerable to Improper Authorization through its Leave Request REST API
Medium Also affects dolibarr/dolibarr
GHSA-hxmh-2xc4-c894
Dolibarr ERP CRM contains a remote code evaluation vulnerability
Critical Also affects dolibarr/dolibarr
GHSA-jggh-5rmh-r6h5
Dolibarr has Insufficient Verification of Data Authenticity
Low Also affects dolibarr/dolibarr
GHSA-rvwr-q5hj-wq7g
Dolibarr has an Injection issue
Medium Also affects dolibarr/dolibarr
GHSA-j2g9-rprv-hrhc
Dolibarr user with permission to edit PHP content can bypass filtering to restrict dangerous PHP functions
High Also affects dolibarr/dolibarr
GHSA-676v-wh57-p375
Dolibarr Allows Code Injection through its Website Module
High Also affects dolibarr/dolibarr
GHSA-w5j3-8fcr-h87w
Dolibarr: OS Command Injection (RCE) via MAIN_ODT_AS_PDF configuration
Critical Also affects dolibarr/dolibarr
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor