Goal Reached Thanks to every supporter β€” we hit 100%!

Goal: 1000 CNY Β· Raised: 1000 CNY

100.0%

CVE-2025-64420 β€” AI Deep Analysis Summary

CVSS 10.0 Β· Critical

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.…

Q2Root Cause? (CWE/Flaw)

πŸ›‘οΈ **CWE**: CWE-522 (Insufficiently Protected Credentials). πŸ” **Flaw**: The application fails to restrict access to sensitive cryptographic material.…

Q3Who is affected? (Versions/Components)

πŸ“¦ **Vendor**: coollabsio. πŸ“¦ **Product**: Coolify (Open-source Heroku/Netlify/Vercel alternative). πŸ“… **Affected Versions**: v4.0.0-beta.434 and all earlier versions. 🚫 Newer versions are likely safe. βœ…

Q4What can hackers do? (Privileges/Data)

πŸ”‘ **Privileges**: Escalates from Low-Privilege to **Root**. πŸ“‚ **Data**: Exposes Root User SSH Private Keys.…

Q5Is exploitation threshold high? (Auth/Config)

πŸ”“ **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. πŸƒβ€β™‚οΈ