CVE-2022-24784
Summary
| CVE | CVE-2022-24784 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2022-03-25 22:15:00 UTC |
| Updated | 2023-06-30 18:51:00 UTC |
| Description | Statamic is a Laravel and Git powered CMS. Before versions 3.2.39 and 3.3.2, it is possible to confirm a single character of a user's password hash using a specially crafted regular expression filter in the users endpoint of the REST API. Multiple such requests can eventually uncover the entire hash. The hash is not present in the response, however the presence or absence of a result confirms if the character is in the right position. The API has throttling enabled by default, making this a time intensive task. Both the REST API and the users endpoint need to be enabled, as they are disabled by default. The issue has been fixed in versions 3.2.39 and above, and 3.3.2 and above. |
Risk And Classification
Problem Types: CWE-203
NVD Known Affected Configurations (CPE 2.3)
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Prevent filtering users by password hashes in the APIs by jasonvarga · Pull Request #5568 · statamic/cms · GitHub | MISC | github.com | |
| Prevent filtering users by password hashes in the APIs by jasonvarga · Pull Request #5604 · statamic/cms · GitHub | MISC | github.com | |
| Discoverability of user password hash via REST API · Advisory · statamic/cms · GitHub | CONFIRM | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.