Q: Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: **Missing Authorization** check. 🔍 **CWE**: CWE-200 (Information Exposure). ❌ **Flaw**: No access control on key retrieval endpoints. Any authenticated user can bypass security layers. 🛡️

Q: Who is affected? (Versions/Components)

👥 **Affected**: **Coolify** (Self-hosted PaaS). 📦 **Version**: All versions **before 4.0.0-beta.374**. 🏢 **Vendor**: coollabsio. ⚠️ **Scope**: Users running older beta or stable builds. 👥

Q: Is exploitation threshold high? (Auth/Config)

⚖️ **Threshold**: **LOW**. 🔑 **Auth**: Requires **Authentication**. ⚙️ **Config**: No special config needed. 🎯 **Ease**: Simple API call if logged in. Not zero-day. ⚖️

Q: Is there a public Exp? (PoC/Wild Exploitation)

🌐 **Public Exp?**: **No PoC** listed. 📜 **Status**: Advisory published. 🔥 **Wild Exp**: Unlikely yet. 👀 **Watch**: Monitor GitHub advisories for proof-of-concept releases. 🌐

Q: How to self-check? (Features/Scanning)

🔍 **Self-Check**: Scan for Coolify instances. 📊 **Version**: Verify version < 4.0.0-beta.374. 🕵️ **Test**: Try accessing key endpoints with valid creds. 🛠️ **Tools**: Use DAST scanners for auth bypass. 🔍

Q: Is it fixed officially? (Patch/Mitigation)

✅ **Fixed**: **Yes**. 🔧 **Patch**: Upgrade to **4.0.0-beta.374** or later. 📥 **Source**: GitHub Security Advisory (GHSA-wg8x-cgq4-vjxj). 🔄 **Action**: Immediate update required. ✅

Q: Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **HIGH**. 🚨 **Priority**: Patch ASAP. ⚠️ **Risk**: CVSS High (C:H, I:H, A:H). 📢 **Action**: Critical security update. Do not delay. 🔥

Question 1

What is this vulnerability? (Essence + Consequences)

Accepted Answer

🚨 **Essence**: Coolify < 4.0.0-beta.374 leaks private keys in **plaintext**.
📉 **Consequences**: Total compromise of infrastructure security. Attackers gain full access to sensitive credentials.…

Question 2

Root Cause? (CWE/Flaw)

Accepted Answer

🛡️ **Root Cause**: **Missing Authorization** check.
🔍 **CWE**: CWE-200 (Information Exposure).
❌ **Flaw**: No access control on key retrieval endpoints. Any authenticated user can bypass security layers. 🛡️

Question 3

Who is affected? (Versions/Components)

Accepted Answer

👥 **Affected**: **Coolify** (Self-hosted PaaS).
📦 **Version**: All versions **before 4.0.0-beta.374**.
🏢 **Vendor**: coollabsio.
⚠️ **Scope**: Users running older beta or stable builds. 👥

Question 4

What can hackers do? (Privileges/Data)

Accepted Answer

💻 **Hackers Can**: Retrieve **ANY** existing private key.
🔓 **Privileges**: Acts as an authenticated user.
📂 **Data**: Accesses instance secrets in **plaintext**.…

Question 5

Is exploitation threshold high? (Auth/Config)

Accepted Answer

⚖️ **Threshold**: **LOW**.
🔑 **Auth**: Requires **Authentication**.
⚙️ **Config**: No special config needed.
🎯 **Ease**: Simple API call if logged in. Not zero-day. ⚖️

Question 6

Is there a public Exp? (PoC/Wild Exploitation)

Accepted Answer

🌐 **Public Exp?**: **No PoC** listed.
📜 **Status**: Advisory published.
🔥 **Wild Exp**: Unlikely yet.
👀 **Watch**: Monitor GitHub advisories for proof-of-concept releases. 🌐

Question 7

How to self-check? (Features/Scanning)

Accepted Answer

🔍 **Self-Check**: Scan for Coolify instances.
📊 **Version**: Verify version < 4.0.0-beta.374.
🕵️ **Test**: Try accessing key endpoints with valid creds.
🛠️ **Tools**: Use DAST scanners for auth bypass. 🔍

Question 8

Is it fixed officially? (Patch/Mitigation)

Accepted Answer

✅ **Fixed**: **Yes**.
🔧 **Patch**: Upgrade to **4.0.0-beta.374** or later.
📥 **Source**: GitHub Security Advisory (GHSA-wg8x-cgq4-vjxj).
🔄 **Action**: Immediate update required. ✅

Question 9

What if no patch? (Workaround)

Accepted Answer

🚧 **No Patch?**: Rotate all private keys immediately.
🔒 **Mitigation**: Restrict user access levels.
🛑 **Block**: Disable key retrieval endpoints if possible.…

Question 10

Is it urgent? (Priority Suggestion)

Accepted Answer

🔥 **Urgency**: **HIGH**.
🚨 **Priority**: Patch ASAP.
⚠️ **Risk**: CVSS High (C:H, I:H, A:H).
📢 **Action**: Critical security update. Do not delay. 🔥

Goal Reached Thanks to every supporter — we hit 100%!

CVE-2025-22612 — AI Deep Analysis Summary

Q1What is this vulnerability? (Essence + Consequences)

Q2Root Cause? (CWE/Flaw)

Q3Who is affected? (Versions/Components)

Q4What can hackers do? (Privileges/Data)

Q5Is exploitation threshold high? (Auth/Config)

Q6Is there a public Exp? (PoC/Wild Exploitation)

Q7How to self-check? (Features/Scanning)

Q8Is it fixed officially? (Patch/Mitigation)

Q9What if no patch? (Workaround)

Q10Is it urgent? (Priority Suggestion)

Continue exploring