Skip to content

XWiki Platform Improper Authorization check for inactive users

High severity GitHub Reviewed Published Sep 8, 2022 in xwiki/xwiki-platform • Updated Jan 27, 2023

Package

maven org.xwiki.platform:xwiki-platform-oldcore (Maven)

Affected versions

>= 1.1, < 13.10.5
>= 14.0, < 14.3-rc-1

Patched versions

13.10.5
14.3-rc-1

Description

Impact

Some resources are missing a check for inactive (not yet activated or disabled) users in XWiki, including the REST service: so a disabled user can enable themselves using a REST call. On the same way some resources handler created by extensions are not protected by default: so an inactive users could perform actions for such extensions.

This issue exists since at least version 1.1 of XWiki for instance configured with the email activation required for new users. Now it's more critical for newer versions (>= 11.3RC1) since we provided the capability to disable user without deleting them, and we encouraged using that feature.

Patches

This issue has been patched in XWiki 14.3RC1 and XWiki 13.10.5.

Workarounds

There is no workaround for this other than upgrading XWiki.

References

For more information

If you have any questions or comments about this advisory:

References

@surli surli published to xwiki/xwiki-platform Sep 8, 2022
Published by the National Vulnerability Database Sep 8, 2022
Published to the GitHub Advisory Database Sep 16, 2022
Reviewed Sep 16, 2022
Last updated Jan 27, 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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:U/C:H/I:H/A:N

EPSS score

0.110%
(46th percentile)

Weaknesses

CVE ID

CVE-2022-36090

GHSA ID

GHSA-jgc8-gvcx-9vfx

Source code

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