Question 1

What is this vulnerability? (Essence + Consequences)

Accepted Answer

🚨 **Essence**: GitHub Enterprise Server (GHES) has an **Unsafe Reflection** vulnerability.…

Question 2

Root Cause? (CWE/Flaw)

Accepted Answer

🛡️ **Root Cause**: **CWE-470** (Use of Externally-Controlled Input to Select Class or Code).…

Question 3

Who is affected? (Versions/Components)

Accepted Answer

📦 **Affected**: All versions of **GitHub Enterprise Server** prior to **3.12**.
✅ **Fixed Versions**: 3.8.13, 3.9.8, 3.10.5, and 3.11.3.
🏢 **Target**: Self-hosted GitHub Enterprise deployments.

Question 4

What can hackers do? (Privileges/Data)

Accepted Answer

💀 **Attacker Capabilities**:
1. **Execute User-Controlled Methods**: Run arbitrary code logic.
2. **Remote Code Execution (RCE)**: Take full control of the server.
3.…

Question 5

Is exploitation threshold high? (Auth/Config)

Accepted Answer

🔒 **Exploitation Threshold**: **HIGH**.
👤 **Requirement**: Attacker must be **logged in** with the **Organization Owner** role on the GHES instance.…

Question 6

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

Accepted Answer

📜 **Public Exploit**: Yes, **PoC available**.
🔗 **Source**: ProjectDiscovery Nuclei Templates (`CVE-2024-0200.yaml`).
🌍 **Status**: Detection templates are public, making scanning easy for threat actors.

Question 7

How to self-check? (Features/Scanning)

Accepted Answer

🔍 **Self-Check**:
1. Check your GHES version against the fixed list (3.8.13+, 3.9.8+, etc.).
2. Use **Nuclei** with the specific CVE template to scan for reflection injection patterns.
3.…

Question 8

Is it fixed officially? (Patch/Mitigation)

Accepted Answer

🛠️ **Official Fix**: **YES**.
📅 **Published**: Jan 16, 2024.
🔄 **Action**: Upgrade to **3.8.13**, **3.9.8**, **3.10.5**, or **3.11.3** (or newer 3.12+).
📖 **Refs**: GitHub Admin Release Notes.

Question 9

What if no patch? (Workaround)

Accepted Answer

🚧 **No Patch? Workaround**:
1. **Restrict Access**: Immediately revoke **Organization Owner** privileges for non-essential users.
2. **Network Segmentation**: Isolate GHES instances from untrusted networks.…

Question 10

Is it urgent? (Priority Suggestion)

Accepted Answer

🔥 **Urgency**: **HIGH**.
⚡ **Priority**: Patch immediately if you have Owner accounts with compromised credentials.
📉 **Risk**: While auth is required, RCE impact is severe.…

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

CVE-2024-0200 — 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