Skip to content

It's possible to execute anything with superadmin right through comments and async macro

Critical
tmortagne published GHSA-9cqm-5wf7-wcj7 Mar 1, 2023

Package

maven org.xwiki.platform:xwiki-platform-rendering-async-macro (Maven)

Affected versions

>= 11.6-rc-1

Patched versions

14.9, 14.4.6, 13.10.10

Description

Impact

Comments are supposed to be executed with the right of superadmin but in restricted mode (anything dangerous is disabled) but the async macro is not taking into account the restricted mode.

This means that any user with comment right can use the async macro to make it execute any wiki content with the right of superadmin as in:

{{async}}
{{groovy}}println "it works !"{{/groovy}}
{{/async}}

Patches

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

Workarounds

The only known workaround consists in applying the following patch and rebuilding and redeploying org.xwiki.platform:xwiki-platform-rendering-async-macro.

References

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-26471

Weaknesses