# CVE-2024-52307: authentik allows a timing attack due to missing constant time comparison for metrics view

> Attackers can brute-force the SECRET_KEY via timing attacks on the metrics endpoint, potentially bypassing authentication or accessing sensitive data.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Nov 2024
- **Updated:** 27 Nov 2024
- **Also known as:** BIT-authentik-2024-52307, GHSA-2xrw-5f2x-m56j

## What is CVE-2024-52307?

CVE-2024-52307 is a medium-severity vulnerability in goauthentik authentik, published on 21 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-208 (Observable Timing Discrepancy)

## Which versions are affected by CVE-2024-52307?

1 open source package ship an affected version, including authentik. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `authentik` | Bitnami | All versions | 2024.8.5, 2024.10.3 |

Products: Goauthentik Authentik.

## How do I fix CVE-2024-52307?

Upgrade authentik to a fixed version for your release line: 2024.8.5 or 2024.10.3.

## Is CVE-2024-52307 being exploited?

There is no known exploitation of CVE-2024-52307 in the wild and no public exploit code.

## Other vulnerabilities in goauthentik authentik

- [CVE-2026-49448](https://insights.sbomify.com/CVE-2026-49448/): authentik: SourceStage bypass via empty POST (critical 9.8)
- [CVE-2023-46249](https://insights.sbomify.com/CVE-2023-46249/): authentik potential installation takeover when default admin user is deleted (critical 9.7)
- [CVE-2022-23555](https://insights.sbomify.com/CVE-2022-23555/): authentik vulnerable to Improper Authentication via invitation URL token reuse (critical 9.4)
- [CVE-2026-42849](https://insights.sbomify.com/CVE-2026-42849/): authentik: Reflected XSS in SFE AutosubmitStage allows IDP account takeover (critical 9.3)
- [CVE-2026-25227](https://insights.sbomify.com/CVE-2026-25227/): authentik affected by Remote Code Execution via Context Key Injection in PropertyMapping Test Endpoint (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-52307 and fix it if it is affected.

What it is: CVE-2024-52307 is a medium-severity vulnerability in goauthentik authentik, published on 21 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-52307 in the wild and no public exploit code.

Affected packages and fixed versions:
- authentik (Bitnami): affected all versions; fixed in 2024.8.5, 2024.10.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-52307/ (Markdown: https://insights.sbomify.com/CVE-2024-52307/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-52307
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-52307
- OSV: https://osv.dev/vulnerability/CVE-2024-52307

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-52307/
Summaries are generated and may contain mistakes; the official description above is the record.