GMS-2022-7743
Prometheus can be secured by a web.yml file that specifies usernames and hashed passwords for basic authentication. Passwords are hashed with bcrypt, which means that even if you have access to the hash, it is very hard to find the original password back. However, a flaw in the way this mechanism was implemented in the exporter toolkit makes it possible with people who know the hashed password to authenticate against Prometheus. A request can be forged by an attacker to poison the internal cache used to cache the computation of hashes and make subsequent requests successful. This cache is used in both happy and unhappy scenarios in order to limit side channel attacks that could tell an attacker if a user is present in the file or not.
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| github.com | prometheus/prometheus | 2.24.1, 2.38.0 |
Timeline
- Dec 5, 2022 CVE Published
References
- https://github.com/prometheus/prometheus/security/advisories/GHSA-4v48-4q5m-8vx4 url
- https://github.com/prometheus/prometheus/commit/31a2db3ae9c0f4b486b6895973beabc1d1beac93 patch
- https://github.com/prometheus/prometheus/releases/tag/v2.37.4 url
- https://github.com/prometheus/prometheus/releases/tag/v2.40.4 url
- https://github.com/advisories/GHSA-4v48-4q5m-8vx4 advisory