Skip to content

Privilege escalation in the Sulu Admin panel

High severity GitHub Reviewed Published Dec 15, 2021 in sulu/sulu • Updated Feb 1, 2023

Package

composer sulu/sulu (Composer)

Affected versions

>= 2.0.0, <= 2.2.17
>= 2.3.0, <= 2.3.7
= 2.4.0-RC1

Patched versions

2.2.18
2.3.8
2.4.0

Description

Impact

Impacted are only users which already have access to the admin UI. Over the API it was possible for them to give themselves permissions to areas which they did not already had. This issue was introduced in 2.0.0-RC1 with the new ProfileController putAction.

Patches

The versions have been patched in 2.2.18, 2.3.8 and 2.4.0.

Workarounds

Patching the ProfileController of affected sulu versions yourself by overwriting it.

References

Are there any links users can visit to find out more?

Currently not.

For more information

If you have any questions or comments about this advisory:

References

@alexander-schranz alexander-schranz published to sulu/sulu Dec 15, 2021
Published by the National Vulnerability Database Dec 15, 2021
Reviewed Dec 15, 2021
Published to the GitHub Advisory Database Dec 15, 2021
Last updated Feb 1, 2023

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

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:H

EPSS score

0.104%
(44th percentile)

Weaknesses

CVE ID

CVE-2021-43835

GHSA ID

GHSA-84px-q68r-2fc9

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.