Skip to content

Creation of new database tables through login form on PostgreSQL

High severity GitHub Reviewed Published Nov 21, 2022 in xwiki/xwiki-platform • Updated Jul 10, 2023

Package

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

Affected versions

< 13.10.8
>= 14.0.0, < 14.4.2
>= 14.5.0, < 14.6-rc-1

Patched versions

13.10.8
14.4.2
14.6-rc-1

Description

Impact

It's possible to make XWiki create many new schemas and fill them with tables just by using a crafted user identifier in the login form.

Patches

The problem has been patched in XWiki 13.10.8, 14.6RC1 and 14.4.2.

Workarounds

The only workarounds for this are:

  • use an authenticator which does interpret the login as a reference to a document
  • using a different database than PostgreSQL
  • upgrade XWiki

References

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

For more information

If you have any questions or comments about this advisory:

References

@surli surli published to xwiki/xwiki-platform Nov 21, 2022
Published to the GitHub Advisory Database Nov 21, 2022
Reviewed Nov 21, 2022
Published by the National Vulnerability Database Nov 23, 2022
Last updated Jul 10, 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
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:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.078%
(34th percentile)

Weaknesses

CVE ID

CVE-2022-41932

GHSA ID

GHSA-4x5r-6v26-7j4v

Source code

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