llamaCVEVulnerability Intelligence
/
authentik

CVE-2022-23555

authentik vulnerable to Improper Authentication via invitation URL token reuse

Specific setups onlyParche disponible
Descargar PNG JSON
CVSS 3.1
9.4
Crítica
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L Fuente: CNA
8.8NVD · CVSS 3.1CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
ExplotaciónPoC públicaSSVC: poc · no figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche2 versiones2022.10.4 · 2022.11.4
Exposición1.422 dDesde la divulgación, 27 dic 2022, 7:12 p. m.
Detección1.406 dDesde la divulgación hasta su ingreso al índice
Decisión SSVCAtender
Priorizar en el próximo ciclo de cambios
Existe PoC pública, automatizable e impacto técnico total. Hay versiones corregidas disponibles.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Evaluación SSVC +1
Explotación
Remediación
Monitoreo
Detectada
Fuente: OSV +1
28 dic 22
11 abr 25
3 nov 26
18 nov 26
19 nov 26
28 dic 22
18 dic 23
8 dic 24
28 nov 25
19 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2022-23555 divulgada · CVSS 9.4 (CNA)
Divulgación Evaluación SSVC CISA-ADP · explotación PoC pública
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Monitoreo Fuente: OSV Registro visto por primera vez en OSV
Monitoreo Verificada Última verificación contra las fuentes
Resumen

authentik is an open-source Identity Provider focused on flexibility and versatility. Versions prior to 2022.11.4 and 2022.10.4 are vulnerable to Improper Authentication. Token reuse in invitation URLs leads to access control bypass via the use of a different enrollment flow than in the one provided. The vulnerability allows an attacker that knows different invitation flows names (e.g. `enrollment-invitation-test` and `enrollment-invitation-admin`) via either different invite links or via brute forcing to signup via a single invitation url for any valid invite link received (it can even be a url for a third flow as long as it's a valid invite) as the token used in the `Invitations` section of the Admin interface does NOT change when a different `enrollment flow` is selected via the interface and it is NOT bound to the selected flow, so it will be valid for any flow when used. This issue is patched in authentik 2022.11.4,2022.10.4 and 2022.12.0. Only configurations that use invitations and have multiple enrollment flows with invitation stages that grant different permissions are affected. The default configuration is not vulnerable, and neither are configurations with a single enrollment flow. As a workaround, fixed data can be added to invitations which can be checked in the flow to deny requests. Alternatively, an identifier with high entropy (like a UUID) can be used as flow slug, mitigating the attack vector by exponentially decreasing the possibility of discovering other flows.

Affects authentik before 2022.10.4 and 2022.11.0 through 2022.11.3, in setups with multiple enrollment flows whose invitation stages grant different permissions. Fixed in 2022.10.4 and 2022.11.4.

¿Qué significa?A person holding a valid invitation link can sign up through a different enrollment flow than the one bound to that invitation. They then gain the permissions of that other flow, such as admin group membership.
¿Quién está afectado?Only configurations that use invitations and have multiple enrollment flows with invitation stages granting different permissions are affected. The default configuration and configurations with a single enrollment flow are not vulnerable. To check, review the enrollment flows and invitation stages in the authentik admin interface and compare the installed version against the affected ranges.
¿Qué hacer?Upgrade to authentik 2022.11.4 or 2022.10.4, depending on the release line in use.
Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
Configurations that use invitations and have multiple enrollment flows with invitation stages that grant different permissions.“Only configurations using both invitations and have multiple enrollment flows with invitation stages that grant different permissions are affected.”
02
Single-enrollment-flow configurations and the default configuration are not vulnerable.“The default configuration is not vulnerable, and neither are configurations with a single enrollment flow.”
¿Quién debe revisar?Teams running authentik with invitations and multiple enrollment flows that grant different permissions, such as admin and standard user signup flows.
Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CNA
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
PrivilegiosPR:N
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:L
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida
authentik< 2022.10.4
authentik≥ 2022.11.0 < 2022.11.4
2022.10.4
2022.11.0
2022.11.4
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
authentik
Corregida 2022.10.4, 2022.11.4 — —
Versiones corregidas2022.10.42022.11.4
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Fabricantehttps://github.com/goauthentik/authentik/security/advisories/GHSA-9qwp-jf7p-vr7h

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.