Skip to content

Privilege Chaining with the user admin role in dhis2-core

Moderate
Philip-Larsen-Donnelly published GHSA-59fm-8432-2426 Dec 8, 2022

Package

dhis2-core (none)

Affected versions

2.34, 2.35, 2.36, 2.37, 2.38, 2.39

Patched versions

2.36.12.1, 2.37.8.1, 2.38.2.1, 2.39.0.1

Description

Impact

This is a privilege escalation vulnerability. A DHIS2 user with authority to manage users can assign superuser privileges to themself by manually crafting an HTTP PUT request.

Only users with the following DHIS2 user role authorities can exploit this vulnerability:

  • User (Add/Update/Delete)
  • User Group (Add/Update/Delete)

Note that in many systems the only users with user admin privileges are also superusers. In these cases, the escalation vulnerability does not exist.

The vulnerability is only exploitable by attackers who can authenticate as users with the user admin authority. As this is usually a small and relatively trusted set of users, exploit vectors will often be limited.

Patches

DHIS2 administrators should upgrade to the following hotfix releases:

  • 2.36.12.1
  • 2.37.8.1
  • 2.38.2.1
  • 2.39.0.1

Workarounds

The only known workaround to this issue is to avoid the assignment of the user management authority to any users until the patch has been applied.

For more information

If you have any questions or comments about this advisory, email us at [email protected]

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L

CVE ID

CVE-2022-41948

Weaknesses

Credits