Skip to content

Built-in roles and userAccount_write permission allow ATO and privilege escalation

High
amousset published GHSA-246r-fjcq-548w Aug 25, 2025

Package

No package listed

Affected versions

>= 8.3.0, < 8.3.2

Patched versions

>= 8.3.2

Description

Impact

The userAccount_write permission is included in each built-in roles used in user management and the XML users file /opt/rudder/etc/rudder-users.xml file. Theses roles, such as read_only, compliance, are meant for read-only access to some parts of Rudder, excluding user management.

However, the userAccount_write permission now allows access to the POST /rudder/api/latest/usermanagement/update/{username} endpoint (since 8.3.0 : #5669).

This causes two security breaches :

  1. any user with previously unprivileged roles can do ATO (Account Takeover), by updating the password of another user
  2. any user with previously unprivileged roles can do privilege escalation, by updating its own roles to higher privilege ones (administrator)

Patches

#6386

Workarounds

None

References

Severity

High

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
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

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:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

CVE ID

No known CVE

Weaknesses

No CWEs