Skip to content

Data leak of password hash through change requests

High severity GitHub Reviewed Published Dec 4, 2023 in xwiki-contrib/application-changerequest • Updated Dec 5, 2023

Package

maven org.xwiki.contrib.changerequest:application-changerequest-default (Maven)

Affected versions

>= 0.1, < 1.10

Patched versions

1.10

Description

Impact

Change request allows to edit any page by default, and the changes are then exported in an XML that anyone can download. So it's possible for an attacker to obtain password hash of users by performing edition of the user profiles and then downloading the XML that has been created. This is also true for any document that might contain password field and that a user can view.
This vulnerability impacts all version of Change Request, but the impact depends on the rights that has been set on the wiki since it requires for the user to have the Change request right (allowed by default) and view rights on the page to target.
Also the issue cannot be easily exploited in an automated way.

Patches

The patch consists in denying to users the right of editing pages that contains a password field with change request. It means that already existing change request for those pages won't be removed by the patch, administrators needs to take care of it.

The patch is provided in Change Request 1.10, administrators should upgrade immediately.

Workarounds

It's possible to workaround the vulnerability by denying manually the Change request right on some spaces, such as XWiki space which will include any user profile by default.

References

For more information

If you have any questions or comments about this advisory:

Attribution

Thanks Michael Hamann for the report.

References

@surli surli published to xwiki-contrib/application-changerequest Dec 4, 2023
Published by the National Vulnerability Database Dec 4, 2023
Published to the GitHub Advisory Database Dec 5, 2023
Reviewed Dec 5, 2023
Last updated Dec 5, 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
Changed
Confidentiality
High
Integrity
None
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:C/C:H/I:N/A:N

EPSS score

0.066%
(30th percentile)

Weaknesses

CVE ID

CVE-2023-49280

GHSA ID

GHSA-2fr7-cc7p-p45q

Source code

Credits

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