This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login.
Read the full analysis โ
Q1What is this vulnerability? (Essence + Consequences)
๐จ **Essence**: A critical flaw in Coolify allows low-privilege users to access root user SSH private keys. ๐ **Consequences**: Complete system compromise.โฆ
๐ **Auth Required**: Yes, but **Low** privilege. ๐ **Threshold**: Low. An attacker only needs basic access to the Coolify interface. ๐ถ **Config**: No complex configuration needed. Just valid low-level credentials. โก
Q6Is there a public Exp? (PoC/Wild Exploitation)
๐ **Public Exp**: No specific PoC code provided in the data. ๐ **Status**: Advisory published (GHSA-qwxj-qch7-whpc). ๐ต๏ธ **Risk**: High likelihood of wild exploitation due to simplicity (just reading a file/key). โ ๏ธ
Q7How to self-check? (Features/Scanning)
๐ **Check**: Verify your Coolify version. ๐ **Scan**: Look for unauthorized access to SSH key storage endpoints. ๐ก๏ธ **Audit**: Check if low-privilege users can retrieve root credentials via API or UI. ๐จ
Q8Is it fixed officially? (Patch/Mitigation)
๐ง **Fix**: Upgrade to a version **newer than** v4.0.0-beta.434. ๐ข **Source**: Official GitHub Security Advisory (GHSA-qwxj-qch7-whpc). โ **Action**: Immediate update recommended by vendor. ๐
Q9What if no patch? (Workaround)
๐ง **Workaround**: Restrict low-privilege user permissions strictly. ๐ **Mitigation**: Disable SSH key exposure in UI/API if possible. ๐ **Isolate**: Segregate critical root keys from the application layer. ๐งฑ
Q10Is it urgent? (Priority Suggestion)
๐ฅ **Priority**: **CRITICAL**. ๐จ **Urgency**: Immediate action required. CVSS Score indicates High impact (C:H, I:H, A:H). ๐ **Risk**: Root compromise is game-over for most servers. ๐โโ๏ธ