Skip to content

Privilege escalation (PR) via async macro and IconThemeSheet from the user profile

Critical
tmortagne published GHSA-vwr6-qp4q-2wj7 Mar 1, 2023

Package

maven org.xwiki.platform:xwiki-platform-icon-ui (Maven)

Affected versions

>= 6.2-milestone-1

Patched versions

14.9, 14.4.6, 13.10.10

Description

Impact

One can execute any wiki content with the right of IconThemeSheet author by creating an icon theme with the following content:

}}}
{{async async="true"}}
{{groovy}}
  println("Hello from Groovy!")
{{/groovy}}
{{/async}}
{{{

Can be done by creating a new page or even through the user profile for users not having edit right.

Patches

This has been patched in XWiki 14.9, 14.4.6, and 13.10.10.

Workarounds

An easy workaround is to actually fix the bug in the page IconThemesCode.IconThemeSheet by applying the following modification: 48caf74#diff-2ec9d716673ee049937219cdb0a92e520f81da14ea84d144504b97ab2bdae243R45

References

https://jira.xwiki.org/browse/XWIKI-19731

For more information

If you have any questions or comments about this advisory:

Severity

Critical

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
Low
User interaction
None
Scope
Changed
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:L/UI:N/S:C/C:H/I:H/A:H

CVE ID

CVE-2023-26472

Weaknesses