Vulnerability from bitnami_vulndb
authentik is an open-source identity provider. When using the client_credentials or device_code OAuth grants, it was possible for an attacker to get a token from authentik with scopes that haven't been configured in authentik. authentik 2024.8.5 and 2024.10.3 fix this issue.
{
"affected": [
{
"package": {
"ecosystem": "Bitnami",
"name": "authentik",
"purl": "pkg:bitnami/authentik"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2024.8.5"
},
{
"introduced": "2024.10.0"
},
{
"fixed": "2024.10.3"
}
],
"type": "SEMVER"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
],
"aliases": [
"CVE-2024-52287"
],
"database_specific": {
"cpes": [
"cpe:2.3:a:goauthentik:authentik:*:*:*:*:*:go:*:*"
],
"severity": "High"
},
"details": "authentik is an open-source identity provider. When using the client_credentials or device_code OAuth grants, it was possible for an attacker to get a token from authentik with scopes that haven\u0027t been configured in authentik. authentik 2024.8.5 and 2024.10.3 fix this issue.",
"id": "BIT-authentik-2024-52287",
"modified": "2026-09-10T15:46:03.895Z",
"published": "2026-04-16T23:36:20.916Z",
"references": [
{
"type": "FIX",
"url": "https://github.com/goauthentik/authentik/commit/e9c29e1644e9199b4ba58d2b10eb8c322138eea2"
},
{
"type": "ADVISORY",
"url": "https://github.com/goauthentik/authentik/security/advisories/GHSA-v6m7-8j37-8f4v"
},
{
"type": "WEB",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-52287"
}
],
"schema_version": "1.6.2",
"summary": "authentik performs insufficient validation of OAuth scopes"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.