CVE Vulnerabilities

CVE-2023-50719

Cleartext Storage of Sensitive Information

Published: Dec 15, 2023 | Modified: Dec 19, 2023
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

XWiki Platform is a generic wiki platform. Starting in 7.2-milestone-2 and prior to versions 14.10.15, 15.5.2, and 15.7-rc-1, the Solr-based search in XWiki discloses the password hashes of all users to anyone with view right on the respective user profiles. By default, all user profiles are public. This vulnerability also affects any configurations used by extensions that contain passwords like API keys that are viewable for the attacker. Normally, such passwords arent accessible but this vulnerability would disclose them as plain text. This has been patched in XWiki 14.10.15, 15.5.2 and 15.7RC1. There are no known workarounds for this vulnerability.

Weakness

The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.

Affected Software

Name Vendor Start Version End Version
Xwiki Xwiki 7.3 (including) 14.10.5 (excluding)
Xwiki Xwiki 15.0 (including) 15.5.2 (excluding)
Xwiki Xwiki 7.2-milestone2 (including) 7.2-milestone2 (including)
Xwiki Xwiki 7.2-milestone3 (including) 7.2-milestone3 (including)
Xwiki Xwiki 15.6 (including) 15.6 (including)
Xwiki Xwiki 15.6-rc1 (including) 15.6-rc1 (including)
Xwiki Xwiki 15.7-rc1 (including) 15.7-rc1 (including)

Extended Description

Because the information is stored in cleartext (i.e., unencrypted), attackers could potentially read it. Even if the information is encoded in a way that is not human-readable, certain techniques could determine which encoding is being used, then decode the information. When organizations adopt cloud services, it can be easier for attackers to access the data from anywhere on the Internet. In some systems/environments such as cloud, the use of “double encryption” (at both the software and hardware layer) might be required, and the developer might be solely responsible for both layers, instead of shared responsibility with the administrator of the broader system/environment.

Potential Mitigations

References