Skip to content

GHSA-gpq5-7p34-vqx5 CVE-2023-29526

XWiki Platform's async and display macro allow displaying and interacting with any document in restricted mode

High Maven
Severity
9.9 / 10
High · CVSS 3.1
Exploit chance (EPSS)
1.14%
Chance of exploitation in the next 30 days. Higher than 66.73% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-284 Improper Access Control
CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Fix
Available
2 packages have a fixed version

Description

Impact

It's possible to display any page you cannot access through the combination of the async and display macro.

Steps to reproduce:

  1. Enable comments for guests by giving guests comment rights
  2. As a guest, create a comment with content {{async}}{{display reference="Menu.WebHome" /}}{{/async}}
  3. Open the comments viewer from the menu (appends ?viewer=comments to the URL)

-> the Menu.WebHome is displayed while the expectation would be to have an error that the current user is not allowed to see it

Patches

The vulnerability has been patched in XWiki 15.0-rc-1, 14.10.3, 14.4.8, and 13.10.11.

Workarounds

There is no known workaround.

References

https://jira.xwiki.org/browse/XWIKI-20394 https://jira.xwiki.org/browse/XRENDERING-694

For more information

If you have any questions or comments about this advisory:

Affected versions

Maven

PackageVulnerableFixed in
org.xwiki.platform:xwiki-platform-oldcore
>= 10.11.1, < 13.10.11
13.10.11
org.xwiki.platform:xwiki-platform-oldcore
>= 14.0-rc-1, < 14.4.8
14.4.8
org.xwiki.platform:xwiki-platform-oldcore
>= 14.5, < 14.10.3
14.10.3
org.xwiki.platform:xwiki-platform-rendering-async-macro
>= 10.11.1, < 13.10.11
13.10.11
org.xwiki.platform:xwiki-platform-rendering-async-macro
>= 14.0-rc-1, < 14.4.8
14.4.8
org.xwiki.platform:xwiki-platform-rendering-async-macro
>= 14.5, < 14.10.3
14.10.3

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.xwiki.platform:xwiki-platform-oldcore Maven → 13.10.11

maven
<dependency><groupId>org.xwiki.platform</groupId><artifactId>xwiki-platform-oldcore</artifactId><version>13.10.11</version></dependency>
gradle
implementation("org.xwiki.platform:xwiki-platform-oldcore:13.10.11")

org.xwiki.platform:xwiki-platform-rendering-async-macro Maven → 13.10.11

maven
<dependency><groupId>org.xwiki.platform</groupId><artifactId>xwiki-platform-rendering-async-macro</artifactId><version>13.10.11</version></dependency>
gradle
implementation("org.xwiki.platform:xwiki-platform-rendering-async-macro:13.10.11")

Severity breakdown

CVSS 3.1 9.9

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-284: Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

How to prevent it
  • Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.

How to prevent it
  • Requirements: Programming languages and supporting technologies might be chosen which are not subject to these issues.
  • Implementation: Utilize an appropriate mix of allowlist and denylist parsing to filter control-plane syntax from all input.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-qj4x-9g63-25g6
XWiki Platform Old Core: Resource path traversal via /skin/ action endpoint in Jetty 12+
High Also affects org.xwiki.platform:xwiki-platform-oldcore
GHSA-mrqg-xmgm-rc5g
XWiki's REST APIs can list all pages/spaces, leading to unavailability
High Also affects org.xwiki.platform:xwiki-platform-oldcore
GHSA-h259-74h5-4rh9
XWiki vulnerable to remote code execution with script right through unprotected Velocity scripting API
Critical Also affects org.xwiki.platform:xwiki-platform-oldcore
GHSA-57q2-6cp4-9mq3
XWiki exposes passwords and emails stored in fields not named password/email in xml.vm
Medium Also affects org.xwiki.platform:xwiki-platform-oldcore
GHSA-r38m-cgpg-qj69
XWiki leaks password hashes and other accessible password properties
Medium Also affects org.xwiki.platform:xwiki-platform-oldcore
GHSA-p9qm-p942-q3w5
XWiki Platform vulnerable to SQL injection through XWiki#searchDocuments API
Critical Also affects org.xwiki.platform:xwiki-platform-oldcore
GHSA-jp4x-w9cj-97q7
XWiki allows remote code execution through preview of XClass changes in AWM editor
High Also affects org.xwiki.platform:xwiki-platform-oldcore
GHSA-prwh-7838-xf82
XWiki allows SQL injection in query endpoint of REST API with Oracle
Critical Also affects org.xwiki.platform:xwiki-platform-oldcore
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor