Skip to content

A user without PR can reset user authentication failures information

Low severity GitHub Reviewed Published Jul 1, 2021 in xwiki/xwiki-platform • Updated Jan 27, 2023

Package

maven org.xwiki.platform:xwiki-platform-security-authentication-script (Maven)

Affected versions

>= 11.6, < 12.6.8
>= 12.7, < 12.10.4

Patched versions

12.6.8
12.10.4

Description

Impact

The script service method used to reset the authentication failures record can be executed by any user with Script rights and does not require Programming rights as it should have.
Note that being able to reset the authentication failure record mean that an attacker with script right might use it to try performing a bruteforce attack since she'd been able to virtually deactivate the mechanism introduced to mitigate those attacks.

Patches

The problem has been patched in version 12.6.8, 12.10.4 and 13.0.

Workarounds

There's no workaround besides upgrading and being careful on which user should have Script right access. Note that any bruteforce attack on the authentication should be visible in the logs since the authentication failures are logged.

References

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

For more information

If you have any questions or comments about this advisory:

References

@surli surli published to xwiki/xwiki-platform Jul 1, 2021
Published by the National Vulnerability Database Jul 1, 2021
Reviewed Jul 2, 2021
Published to the GitHub Advisory Database Jul 2, 2021
Last updated Jan 27, 2023

Severity

Low

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
High
Privileges required
High
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
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:H/PR:H/UI:R/S:U/C:N/I:L/A:N

EPSS score

0.054%
(24th percentile)

Weaknesses

CVE ID

CVE-2021-32729

GHSA ID

GHSA-m738-3rc4-5xv3

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.