CVE-2024-52307
authentik allows a timing attack due to missing constant time comparison for metrics view
We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.
Please see our statement on Data Privacy.
authentik allows a timing attack due to missing constant time comparison for metrics view
authentik is an open-source identity provider. Due to the usage of a non-constant time comparison for the /-/metrics/ endpoint it was possible to brute-force the SECRET_KEY, which is used to authenticate the endpoint. The /-/metrics/ endpoint returns Prometheus metrics and is not intended to be accessed directly, as the Go proxy running in the authentik server container fetches data from this endpoint and serves it on a separate port (9300 by default), which can be scraped by Prometheus without being exposed publicly. authentik 2024.8.5 and 2024.10.3 fix this issue. Since the /-/metrics/ endpoint is not intended to be accessed publicly, requests to the endpoint can be blocked by the reverse proxy/load balancer used in conjunction with authentik.
Reserved 2024-11-06 | Published 2024-11-21 | Updated 2024-11-27 | Assigner GitHub_MCWE-208: Observable Timing Discrepancy
github.com/...hentik/security/advisories/GHSA-2xrw-5f2x-m56j
github.com/...ommit/5ea4580884f99369f0ccfe484c04cb03a66e65b8
Support options
