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**: Coolify suffers from **OS Command Injection**. π **Consequences**: Attackers can execute arbitrary system commands, leading to total server compromise, data theft, or service disruption.β¦
π‘οΈ **Root Cause**: **CWE-78** (OS Command Injection). The flaw lies in **improper input sanitization** of the **Git Repository field**. Malicious payloads in this field bypass checks and execute as shell commands.
Q3Who is affected? (Versions/Components)
π’ **Affected**: **Coolify** (by coollabsio). π **Versions**: All versions **prior to 4.0.0-beta.420.7**. If you are running an older beta or stable release, you are vulnerable.
Q4What can hackers do? (Privileges/Data)
π **Attacker Capabilities**: With access, hackers gain **High** impact on Confidentiality, Integrity, and Availability.β¦
π¦ **Public Exploit**: **No**. The `pocs` array is empty. While the advisory is public, there is no confirmed public Proof-of-Concept (PoC) or widespread wild exploitation yet. Stay vigilant.
Q7How to self-check? (Features/Scanning)
π **Self-Check**: Scan for **Coolify** instances. Check if the **Git Repository** input field is present. Look for version numbers < **4.0.0-beta.420.7**.β¦
β **Official Fix**: **Yes**. The vendor has issued a security advisory (GHSA-5cg9-38qj-8mc3). The fix is included in version **4.0.0-beta.420.7** and later. Update immediately.
Q9What if no patch? (Workaround)
π§ **No Patch Workaround**: If you cannot update, **strictly sanitize** the Git Repository input field. Implement allow-lists for valid repository URLs.β¦
β‘ **Urgency**: **HIGH**. CVSS Vector shows **H** (High) impact across all categories. As an open-source PaaS alternative, trust is key. Patch immediately to prevent potential remote code execution by low-privilege users.