apache / apache/cloudstack

[Hardening] F-04: Insecure Default 2FA Provider Configuration (Opt-In Instead of Opt-Out).

Abierto
#13,336 0 comentarios 0 reacciones 0 asignados Ver en GitHub
hardening
Lenguaje dominante
Java
Estrellas
3.1k
Forks
1.4k
Merge medio
6 d 19 h
PR fusionados (30 d)
32

Descripción

### The required feature described as a wish

Image

**Description:** A Static PIN is no more secure than a password. Arguably, it is not even a second factor at all, but merely a second step in the authentication process (more on this in the following findings). There may be cases where TOTP is not a viable option, and a Static PIN serves as an alternative. However, Static PIN should not be offered out-of-the-box or listed as an option, as users will naturally follow the path of least resistance toward the weaker method.

**Affected Components:** Management UI

**Impact:** The Static PIN makes the second factor as static and reusable as the password, defeating the purpose of 2FA. An attacker who obtains the PIN once retains persistent access. Replay attacks will succeed indefinitely, and the PIN is vulnerable to the same attacks as a password.

**Steps to Reproduce:**
- Log in to the CloudStack Management UI as a Root Admin.
- Navigate to Configuration > Global Settings.
- Search for `user.2fa.default.provider`, `user.2fa.providers.order`, and `user.2fa.providers.exclude`.
- Observe that Static PIN is not excluded and may be presented as a selectable option.

**Recommended Remediation:** Adopt a secure-by-default, opt-out model: set `user.2fa.default.provider` to TOTP, set `user.2fa.providers.order` to TOTP only by default, and add the Static PIN provider to `user.2fa.providers.exclude` unless explicitly re-enabled by an administrator.

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Comience en el flujo de la Management UI para Configuration > Global Settings y siga cómo se definen y presentan user.2fa.default.provider, user.2fa.providers.order y user.2fa.providers.exclude. Se considera completado cuando TOTP es el proveedor predeterminado y el único proveedor incluido de forma predeterminada en el orden, mientras que Static PIN está excluido, a menos que un administrador lo vuelva a habilitar explícitamente; verifique las tres configuraciones en la UI.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Área
authentication, security
Tipo de issue
Error
Dificultad
3/5
Tiempo estimado
1-2 días
Estado de actividad
Tranquilo
Claridad
Bastante claro
Aptitud para principiantes
55/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.