Skip to content

XWiki Platform vulnerable to Code Injection in icon themes

Critical severity GitHub Reviewed Published Jun 29, 2023 in xwiki/xwiki-platform • Updated Nov 12, 2023

Package

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

Affected versions

>= 6.2-milestone-1, < 14.10.6
>= 15.0-rc-1, < 15.2-rc-1

Patched versions

14.10.6
15.2-rc-1
maven org.xwiki.platform:xwiki-platform-icon-script (Maven)
>= 6.2-milestone-1, < 14.10.6
>= 15.0-rc-1, < 15.2-rc-1
14.10.6
15.2-rc-1
maven org.xwiki.platform:xwiki-platform-icon-ui (Maven)
>= 6.2-milestone-1, < 14.10.6
>= 15.0-rc-1, < 15.2-rc-1
14.10.6
15.2-rc-1

Description

Impact

By either creating a new or editing an existing document with an icon set, an attacker can inject XWiki syntax and Velocity code that is executed with programming rights and thus allows remote code execution. There are different attack vectors, the simplest is the Velocity code in the icon set's HTML or XWiki syntax definition. The icon picker can be used to trigger the rendering of any icon set. The XWiki syntax variant of the icon set is also used without any escaping in some documents, allowing to inject XWiki syntax including script macros into a document that might have programming right, for this the currently used icon theme needs to be edited. Further, the HTML output of the icon set is output as JSON in the icon picker and this JSON is interpreted as XWiki syntax, allowing again the injection of script macros into a document with programming right and thus allowing remote code execution. This impacts the confidentiality, integrity and availability of the whole XWiki instance.

Patches

This has been patched in XWiki 14.10.6 and 15.1. Icon themes now require script right and the code in the icon theme is executed within the context of the icon theme, preventing any rights escalation. A macro for displaying icons has been introduced to avoid injecting the raw wiki syntax of an icon set into another document.

Workarounds

There are no workarounds apart from upgrading to a version containing the fix.

References

References

@michitux michitux published to xwiki/xwiki-platform Jun 29, 2023
Published by the National Vulnerability Database Jun 29, 2023
Published to the GitHub Advisory Database Jun 30, 2023
Reviewed Jun 30, 2023
Last updated Nov 12, 2023

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

EPSS score

1.205%
(86th percentile)

Weaknesses

CVE ID

CVE-2023-36470

GHSA ID

GHSA-fm68-j7ww-h9xf

Source code

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