davift opened a new issue, #14721: URL: https://github.com/apache/cloudstack/issues/14721
### problem <img width="780" height="240" alt="image" src="https://github.com/user-attachments/assets/49c0190b-8765-4d9e-98e2-7fe4433d9d31" /> **Description:** During the 2FA authentication flow (and not limited to it), sensitive parameters, including `codefor2fa` and `sessionkey`, are transmitted as query string parameters in GET requests. This exposes these values in server-side access logs, WAF and proxy logs, referrer headers, and network monitoring tools. **Affected Components:** Management UI **Impact:** An attacker with access to web server logs, proxy infrastructure, network traffic, or browser history could extract a valid `sessionkey` and use it to hijack an authenticated session, effectively bypassing 2FA entirely. A Static PIN in this position would be permanently compromised upon first interception. **Steps to Reproduce:** - Press F12 to open DevTools in any browser. - Open the Network tab to monitor outgoing requests. - Log in to CloudStack as any user. - On the 2FA challenge page, observe the GET request and confirm that `codefor2fa` appears as a URL query parameter. - While navigating through the UI, confirm that many subsequent GET requests also include `sessionkey` and other sensitive parameters in the URL. **Recommended Remediation:** Refactor the 2FA submission to use HTTP POST with parameters submitted in the request body. Ensure all sensitive parameters are excluded from URL construction. Set appropriate Cache-Control and Pragma headers to prevent browser caching of responses containing sensitive data. ### versions The versions of ACS, hypervisors, storage, network etc.. ### The steps to reproduce the bug 1. 2. 3. ... ### What to do about it? _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
