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

🔍 **Self-Check**: 1. Check Sourcegraph version (< 3.37.0). 2. Verify if `gitserver` is exposed to untrusted networks. 3. Scan for HTTP requests manipulating `core.sshCommand` in git configs.

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

✅ **Fixed**: **Yes**. 🩹 **Patch**: Upgrade to Sourcegraph **v3.37.0** or later. 🔗 **Ref**: GitHub Advisory GHSA-qcmp-fx72-q8q9 and PR #30833.

Q: Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **HIGH**. ⚡ **Priority**: Immediate patching required if gitserver is exposed. CVSS Score is **High** (9.8). RCE risk is severe. Do not ignore!

Question 1

What is this vulnerability? (Essence + Consequences)

Accepted Answer

🚨 **Essence**: Sourcegraph allows attackers to inject arbitrary commands via `git` config.
💥 **Consequences**: Remote Code Execution (RCE). Attackers can run bash commands on the server.…

Question 2

Root Cause? (CWE/Flaw)

Accepted Answer

🛡️ **Root Cause**: CWE-94 (Code Injection).
🔍 **Flaw**: Lack of restriction on `git` config execution. The `core.sshCommand` option is not sanitized, allowing arbitrary bash commands to be passed via HTTP arguments.

Question 3

Who is affected? (Versions/Components)

Accepted Answer

📦 **Affected**: Sourcegraph **Gitserver** service.
📉 **Versions**: Prior to **v3.37.0** (e.g., v3.36.3).
🏢 **Vendor**: Sourcegraph Inc.

Question 4

What can hackers do? (Privileges/Data)

Accepted Answer

💀 **Privileges**: Full RCE on the gitserver host.
📂 **Data**: Complete compromise of the server. Attackers can read/write files, install backdoors, and pivot to other internal systems.

Question 5

Is exploitation threshold high? (Auth/Config)

Accepted Answer

⚠️ **Threshold**: Medium.
🔑 **Auth**: Requires **Low Privileges** (PR:L).
🌐 **Config**: Attacker must be able to send HTTP requests to the internal `gitserver` service.…

Question 6

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

Accepted Answer

🔓 **Exploit**: **Yes**.
📜 **PoC**: Publicly available on GitHub (Altelus1/CVE-2022-23642).
🌍 **Status**: Tested on v3.36.3. PacketStorm links also exist.

Question 7

How to self-check? (Features/Scanning)

Accepted Answer

🔍 **Self-Check**:
1. Check Sourcegraph version (< 3.37.0).
2. Verify if `gitserver` is exposed to untrusted networks.
3. Scan for HTTP requests manipulating `core.sshCommand` in git configs.

Question 8

Is it fixed officially? (Patch/Mitigation)

Accepted Answer

✅ **Fixed**: **Yes**.
🩹 **Patch**: Upgrade to Sourcegraph **v3.37.0** or later.
🔗 **Ref**: GitHub Advisory GHSA-qcmp-fx72-q8q9 and PR #30833.

Question 9

What if no patch? (Workaround)

Accepted Answer

🚧 **Workaround**:
1. **Isolate**: Ensure `gitserver` is **not** accessible from untrusted networks.
2. **Restrict**: Block HTTP requests to the gitserver endpoint from external IPs.
3.…

Question 10

Is it urgent? (Priority Suggestion)

Accepted Answer

🔥 **Urgency**: **HIGH**.
⚡ **Priority**: Immediate patching required if gitserver is exposed. CVSS Score is **High** (9.8). RCE risk is severe. Do not ignore!

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

CVE-2022-23642 — 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