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.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor, which exposes security-relevant information about the state of the product, such as whether a particular operation was successful or not.
Link | Tags |
---|---|
https://github.com/statamic/cms/security/advisories/GHSA-qcgx-7p5f-hxvr | third party advisory |
https://github.com/statamic/cms/issues/5604 | issue tracking third party advisory patch |
https://github.com/statamic/cms/pull/5568 | third party advisory patch |