GHSA-5W43-PP8C-GR85
Backend Session ID Not Regenerated on Login (Session Fixation)
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-5W43-PP8C-GR85 divulgada · CVSS 3.1 (GitHub) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Backend Session ID Not Regenerated on Login (Session Fixation)
The October Rain auth library writes the authenticated user's persistence data into the current session without rotating the session ID. In a scenario where an attacker can plant a specific `october_session` cookie in a victim's browser prior to login, the same cookie would remain valid after the victim authenticates.
Exploitability requires an unrelated primitive that October cannot prevent, plus knowledge of the backend URL. The attacker must first place a chosen session cookie in the victim's browser and induce login while that cookie is in place, and must know the URL of the backend the victim will authenticate against (October CMS supports a configurable and non-default backend URI, so this is not always predictable). In practice the cookie-planting step depends on either a sibling-subdomain cookie tossing scenario (only relevant when the operator has scoped the session cookie to a shared parent domain, which is not the shipped default) or a distinct XSS on the same host (which would already be a higher-severity issue on its own). Absent both preconditions, the missing regeneration is not exploitable.
### Impact
- If the cookie-planting precondition is met, the attacker inherits the victim's authenticated session and permissions
- No exposure in the default configuration where the backend is served from a dedicated host and session cookies are host-scoped
- Session fixation hardening; the reporter's end-to-end takeover assumes attacker-controlled cookie placement, which October cannot itself prevent
### Patches
The vulnerability has been patched in v4.3.4.
### Workarounds
If upgrading immediately is not possible:
- Ensure the session cookie is scoped to the specific backend host rather than a parent domain (set `session.domain` in `config/session.php` to the exact host, not a leading-dot parent)
- Serve the backend from a dedicated hostname that is not shared with untrusted subdomains
### References
- Reported by Elure (Marasescu Mihnea-Luca) and pentest-tools.com
Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
Packagistoctober/system |
Corregida | 4.3.3 | — | — |
4.3.3Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/octobercms/october/security/advisories/GHSA-5w43-pp8c-gr85Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
