Failure to Initialize a Secure Transport Layer (TLS) During Out-of-the-Box Setup.
- 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:** TLS is not enabled by default on the Management server or System VMs. This insecure default persists until explicitly remediated by the administrator.
**Affected Component:** Management UI / API, SSVM, CPVM
**Impact:** An attacker with network access can trivially intercept or sniff management traffic, including administrator credentials (password and 2FA codes), session tokens, API keys, and sensitive configuration data.
**Steps to Reproduce:**
- Deploy ACS following the official documentation.
- Navigate to http://:8080/ (no HTTPS redirect occurs).
- Attempt to connect to https://:8443/ and confirm that the connection fails.
- Capture traffic with Wireshark or `tcpdump` during a login session.
- Observe that credentials and session tokens are transmitted in cleartext.
**Recommended Remediation:** Enable TLS by default during installation. A self-signed certificate can be automatically generated and configured without any additional effort on the user's part.
Contributor guide
Research direction
Start by following the official CloudStack deployment documentation and reproduce the HTTP access on port 8080 and failed HTTPS access on port 8443. Review the out-of-the-box setup for the Management UI/API, SSVM, and CPVM; done means TLS is enabled by default and management traffic is not exposed in cleartext.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100