GHSA-RPV9-QP4C-G469
Back-office account takeover via sign-in redirect manipulation in Umbraco CMS
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-RPV9-QP4C-G469 divulgada · CVSS 8.8 (GitHub) | |
| Divulgación | Modificada | Última actualización del registro | |
| Remediación | Parche 18.2.2 | Umbraco.Cms · 0 d desde divulgación | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Impact
Several weaknesses in the back-office sign-in flow can be combined so that a back-office user's session is handed to an attacker.
Who is impacted. This affects sites running affected versions where the web server or hosting setup passes requests for unrecognised host names through to Umbraco. This is common when Umbraco runs on Kestrel directly, in IIS without host name bindings, or behind a reverse proxy that forwards the `Host` header unchanged. Sites where only the expected host names reach the application are not exposed to the full chain.
No account is needed to prepare the attack. To complete it, a signed-in back-office user has to open a link supplied by the attacker.
What the exposure is. If it succeeds, the attacker gets an authenticated back-office session with the privileges of the user who opened the link. If that user is an administrator, the attacker gets full control of the back-office. That includes reading and changing all content, users and configuration. It can also lead to code execution on the server through features available to administrators.
Patches
The back-office sign-in flow now only accepts redirect destinations on the host serving the request, or on hosts that are explicitly configured. The handling of sign-in codes has also been hardened, so a code can only be returned to and redeemed by the back-office itself. The redirect change also protects sites whose stored sign-in configuration has already been tampered with before the upgrade.
Workarounds
There is no configuration setting that resolves this issue. The following interim measures reduce exposure until you can upgrade:
- Restrict the host names that reach the application. For example, set `AllowedHosts` in `appsettings.json` to the site's own host names, separated by semicolons. You can also bind the web server or reverse proxy to explicit host names, so requests for any other host are rejected before they reach Umbraco.
- Avoid opening back-office links from untrusted sources while signed in to the back-office.
To check whether a site's sign-in configuration has been tampered with, review the redirect addresses stored for the back-office clients. Look for host names that do not belong to the site:
SELECT ClientId, RedirectUris, PostLogoutRedirectUris
FROM umbracoOpenIddictApplications
WHERE ClientId IN ('umbraco-back-office', 'umbraco-swagger')Unrecognised entries are not used once the patch is applied, but you can remove them as housekeeping.
References
- CWE-601: URL Redirection to Untrusted Site ('Open Redirect')
https://cwe.mitre.org/data/definitions/601.html - CWE-346: Origin Validation Error
https://cwe.mitre.org/data/definitions/346.html - CWE-287: Improper Authentication
https://cwe.mitre.org/data/definitions/287.html
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
nugetUmbraco.Cms |
Corregida | 18.2.2 | 0 d | 18.3.1 no afectada |
18.2.2Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-rpv9-qp4c-g469Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
