CVE-2023-36456 json
Authentik lacks Proxy IP headers validation
published 2023-07-06 3 y ago modified 2026-09-08 2 mo ago also BIT-authentik-2023-36456 , EUVD-2023-40420 , GHSA-cmxp-jcw7-jjjv
- cvss
- 8.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
authentik is an open-source Identity Provider. Prior to versions 2023.4.3 and 2023.5.5, authentik does not verify the source of the X-Forwarded-For and X-Real-IP headers, both in the Python code and the go code. Only authentik setups that are directly accessible by users without a reverse proxy are susceptible to this. Possible spoofing of IP addresses in logs, downstream applications proxied by (built in) outpost, IP bypassing in custom flows if used.
This poses a possible security risk when someone has flows or policies that check the user's IP address, e.g. when they want to ignore the user's 2 factor authentication when the user is connected to the company network. A second security risk is that the IP addresses in the logfiles and user sessions are not reliable anymore. Anybody can spoof this address and one cannot verify that the user has logged in from the IP address that is in their account's log. A third risk is that this header is passed on to the proxied application behind an outpost. The application may do any kind of verification, logging, blocking or rate limiting based on the IP address, and this IP address can be overridden by anybody that want to.
Versions 2023.4.3 and 2023.5.5 contain a patch for this issue.
Patch / fix
- bitnami authentik 2023.4.3, 2023.5.5
- goauthentik authentik 2023.4.3, 2023.5.5
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 23 mo ago
Exploit prediction
0.79% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L |
| NVD | 3.1 | 7.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L |
| OSV | 3.1 | 7.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | authentik | <2023.4.3 >=2023.5.0, <2023.5.5 |
2023.4.3 2023.5.5 |
Affected products
- goauthentik authentik
Classification
- Weakness
-
- CWE-436 Interpretation Conflict
References
-
github.com
/goauthentik/authentik/commit/15026748d19d490eb2baf9a9566ead4f805f7dff
patch
-
github.com
/goauthentik/authentik/commit/c07a48a3eccbd7b23026f72136d3392bbc6f795a
patch
-
github.com
/goauthentik/authentik/security/advisories/GHSA-cmxp-jcw7-jjjv
vendor-advisory, advisory
-
goauthentik.io
/docs/releases/2023.4#fixed-in-202343
release-notes, article
-
goauthentik.io
/docs/releases/2023.5#fixed-in-202355
release-notes, article
-
nvd.nist.gov
/vuln/detail/CVE-2023-36456
web
Sources
- CVE List CVE-2023-36456
- NVD CVE-2023-36456
- OSV BIT-authentik-2023-36456
Fencer Vulns 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.