Skip to content

Discoverability of user password hash in Statamic CMS

Low severity GitHub Reviewed Published Mar 25, 2022 in statamic/cms • Updated Jun 30, 2023

Package

composer statamic/cms (Composer)

Affected versions

< 3.2.39
>= 3.3.0, < 3.3.2

Patched versions

3.2.39
3.3.2

Description

Description

It was possible to confirm a single character of a user's password hash (just the hash, not the password) using a specially crafted regular expression filter in the users endpoint of the REST API. Many requests could eventually uncover the entire hash.

The hash would not be in the response, however the presence or absence of a result would confirm if the character was in the right position. It would take a long time since the API has throttling enabled by default.

Additionally, the REST API would need to be enabled, as well as the users endpoint. Both of which are disabled by default.

Resolution

Filtering by password or password hash has been disabled.

Credits

We would like to thank Thibaud Kehler for reporting the issue.

References

@jasonvarga jasonvarga published to statamic/cms Mar 25, 2022
Published by the National Vulnerability Database Mar 25, 2022
Published to the GitHub Advisory Database Mar 29, 2022
Reviewed Mar 29, 2022
Last updated Jun 30, 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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
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:H/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS score

0.106%
(44th percentile)

Weaknesses

CVE ID

CVE-2022-24784

GHSA ID

GHSA-qcgx-7p5f-hxvr

Source code

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