[Hardening] F-02: Default Configuration Forces User’s Posture to Password-Only.
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 1.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 32
Description
### The required feature described as a wish
**Description:** the global configuration setting `enable.user.2fa` defaults to False, meaning users who wish to use two-factor authentication (2FA) cannot do so without a Root Admin first enabling the setting and restarting the management server(s).
**Affected Components:** Management UI
**Impact:** Any compromised or weak user credential is sufficient to gain full access to a user's CloudStack account. This makes the platform susceptible to credential-stuffing, phishing, and brute-force attacks with no second factor to impede unauthorized access.
**Steps to Reproduce:**
- Log in to the CloudStack Management UI as a Root Admin.
- Navigate to Configuration > Global Settings.
- Search for `enable.user.2fa` and observe that its value is set to False.
- Attempt to enable 2FA on your own user account, and confirm that it is not permitted.
**Recommended Remediation:** Change the default value of `enable.user.2fa` to True so that users are always permitted to enroll in 2FA without requiring Root Admin intervention.
Contributor guide
Research direction
Start in the Management UI's Global Settings handling for enable.user.2fa and verify how its default controls user enrollment. The change is done when the default permits users to enroll in 2FA without Root Admin intervention or a management-server restart; confirm the setting and enrollment flow in the UI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100