llamaCVEVulnerability Intelligence
/
Advisory · GitHub · Packagist · getkirby/cms

GHSA-43QQ-QW4X-28F8

Kirby CMS vulnerable to user enumeration in the code-based login and password reset forms

Parche disponible
Descargar PNG JSON
CVSS
—
medium
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche4 versiones3.5.8.2 · 3.6.6.2 · 3.7.5.1 · 3.8.1
Exposición1.493 dDesde la divulgación, 18 oct 2022, 4:14 p. m.
Detección1.490 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Modificada
Explotación
Remediación
Monitoreo
Detectada
18 oct 22
3 feb 26
17 nov 26
20 nov 26
18 oct 22
27 oct 23
3 nov 24
11 nov 25
20 nov 26
FechaFaseEventoDetalle
Divulgación Publicada GHSA-43QQ-QW4X-28F8 divulgada
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Resumen
Descripción del advisory
Texto original · GitHub · en inglés
TL;DR

This vulnerability only affects you if you are using the `code` or `password-reset` auth method with the `auth.methods` option. It can only be successfully exploited under server configuration conditions outside of the attacker's control.

----

Introduction

User enumeration is a type of vulnerability that allows attackers to confirm which users are registered in a Kirby installation. This information can be abused for social engineering attacks against users of the site or to find out the organizational structure of the company.

User enumeration attacks are performed by entering an existing and a non-existing user into the email address field of the login form. If the system returns a different response or behaves differently depending on whether the user exists, the attacker can enter unknown email addresses and use the different behavior as a clue for the (non-)existing user.

Impact

Under normal circumstances, entering an invalid email address results in a "fake" login code form that looks exactly like the one of an existing user (unless debugging is enabled). However, the code that handles the creation of a code challenge (for code-based login or password reset) didn't catch errors that occurred while the challenge request was processed:

  • If the challenge itself runs into an error (e.g. if the email could not be sent), attackers could tell existing users (where the challenge code is called) from non-existing users (where the challenge code is not called and therefore does not output an error).
  • If you are using the `user.login:failed` hook and any exception is thrown within the hook, attackers could see that the user does not exist.

As long as no error occurs during challenge creation and during the processing of the `user.login:failed` hook, your Kirby sites are *not* affected by this vulnerability.

Patches

The problems have been patched in Kirby 3.5.8.2 https://github.com/getkirby/kirby/releases/tag/3.5.8.2, Kirby 3.6.6.2 https://github.com/getkirby/kirby/releases/tag/3.6.6.2, Kirby 3.7.5.1 https://github.com/getkirby/kirby/releases/tag/3.7.5.1 and Kirby 3.8.1 https://github.com/getkirby/kirby/releases/tag/3.8.1. Please update to one of these or a later version https://github.com/getkirby/kirby/releases to fix the vulnerability.

All of the mentioned releases contain two patches for this vulnerability:

  • All errors that occur during the creation of an auth challenge (code-based login or password reset) are swallowed by the backend and only displayed to the user if debugging is enabled.
  • We added a new `auth.debug` option that can be enabled separately from the `debug` option. If disabled, auth errors are only printed to the PHP error log. This ensures that security-critical errors are only displayed if they are really necessary for debugging.
Workarounds

We recommend to update to one of the patch releases. If you cannot update immediately, you can work around the issue by setting the `auth.methods` option to `password`, which disables the code-based login and password reset forms.

However please note that your site will still be vulnerable against another user enumeration issue https://github.com/getkirby/kirby/security/advisories/GHSA-c27j-76xg-6x4f that was also fixed in the same patch releases.

Credits

Thanks to [Florian Merz](mailto:florian@hatchery.io) (@florianmrz) of hatchery.io https://www.hatchery.io/ for responsibly reporting the identified issue.

Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.

Versiones

Rangos afectados

Afectada Corregida
getkirby/cms≥ 3.5.0 < 3.5.8.2
getkirby/cms≥ 3.6.0 < 3.6.6.2
getkirby/cms≥ 3.7.0 < 3.7.5.1
getkirby/cms≥ 3.8.0 < 3.8.1
3.5.0
3.5.8.2
3.6.0
3.6.6.2
3.7.0
3.7.5.1
3.8.0
3.8.1
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
Packagistgetkirby/cms
Corregida 3.5.8.2, 3.6.6.2, 3.7.5.1, 3.8.1 — —
Versiones corregidas3.5.8.23.6.6.23.7.5.13.8.1
Explotación

Arsenal público

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

Referencias
Advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2022-39314
Otrahttps://github.com/getkirby/kirby/security/advisories/GHSA-43qq-qw4x-28f8
Otrahttps://github.com/getkirby/kirby
Otrahttps://github.com/getkirby/kirby/releases/tag/3.5.8.2
Otrahttps://github.com/getkirby/kirby/releases/tag/3.6.6.2
Otrahttps://github.com/getkirby/kirby/releases/tag/3.7.5.1
Otrahttps://github.com/getkirby/kirby/releases/tag/3.8.1

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