CVE-2024-47077 json
authentik cross-provider token validation problems
published 2y ago modified 2mo ago also BIT-authentik-2024-47077 , EUVD-2024-42264 , GHSA-8gfm-pr6x-pfh9
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
Summary
authentik is an open-source identity provider. Prior to versions 2024.8.3 and 2024.6.5, access tokens issued to one application can be stolen by that application and used to impersonate the user against any other proxy provider. Also, a user can steal an access token they were legitimately issued for one application and use it to access another application that they aren't allowed to access. Anyone who has more than one proxy provider application with different trust domains or different access control is affected. Versions 2024.8.3 and 2024.6.5 fix the issue.
Patch / fix
- bitnami authentik 2024.6.5, 2024.8.3
- goauthentik authentik 2024.6.5, 2024.8.3
Is CVE-2024-47077 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| OSV | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | authentik | <2024.6.5 >=2024.8.0, <2024.8.3 |
2024.6.5 2024.8.3 |
Affected products
- goauthentik authentik
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
-
github.com
/goauthentik/authentik/commit/22e586bd8cdc3d1db8a0f18314d76f82371129b2
patch
-
github.com
/goauthentik/authentik/commit/57a31b5dd16d4adce716b9878455c0d6f58155fe
patch
-
github.com
/goauthentik/authentik/security/advisories/GHSA-8gfm-pr6x-pfh9
vendor-advisory, advisory
-
github.com
/goauthentik/authentik/blob/70b5a214f2e7205572f914aaf68682501b9f5945/authentik/providers/oauth2/views/introspe
product, web
-
github.com
/goauthentik/authentik/blob/70b5a214f2e7205572f914aaf68682501b9f5945/internal/outpost/proxyv2/application/auth
product, web
-
nvd.nist.gov
/vuln/detail/CVE-2024-47077
web
Sources
- CVE List CVE-2024-47077
- NVD CVE-2024-47077
- OSV BIT-authentik-2024-47077
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.