Question 1

What is this vulnerability? (Essence + Consequences)

Accepted Answer

🚨 **Essence**: Lightdash suffers from a **Path Traversal** vulnerability.
💥 **Consequences**: Attackers can access files and directories **outside** the web root folder.…

Question 2

Root Cause? (CWE/Flaw)

Accepted Answer

🛡️ **Root Cause**: Insecure file endpoints in the backend routers.…

Question 3

Who is affected? (Versions/Components)

Accepted Answer

📦 **Affected Product**: Lightdash (Visualization Data Analysis Tool).
📉 **Versions**: All versions **before 0.510.3**.
⚠️ **Status**: Vulnerable components include `packages/backend/src/routers`.

Question 4

What can hackers do? (Privileges/Data)

Accepted Answer

🕵️ **Attacker Capabilities**:
1. **Read Arbitrary Files**: Access sensitive data stored outside the web root.
2. **Bypass Restrictions**: Circumvent standard file access controls.
3.…

Question 5

Is exploitation threshold high? (Auth/Config)

Accepted Answer

⚖️ **Exploitation Threshold**: **Low to Medium**.
🔑 **Auth**: Likely requires basic access to the Lightdash interface to trigger the endpoint.…

Question 6

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

Accepted Answer

💣 **Public Exploits**: **Yes**.
📂 **PoCs Available**:
- GitHub PoC by Lserein.
- Nuclei templates by ProjectDiscovery.…

Question 7

How to self-check? (Features/Scanning)

Accepted Answer

🔍 **Self-Check Methods**:
1. **Scan**: Use Nuclei with the CVE-2023-35844 template.
2. **Manual Test**: Send requests with `../` sequences to file endpoints.
3.…

Question 8

Is it fixed officially? (Patch/Mitigation)

Accepted Answer

✅ **Official Fix**: **Yes**.
🔧 **Patch Version**: **0.510.3** and later.
📝 **Commit**: Fixed via commit `fcc808c84c2cc3afb343063e32a49440d32a553c` (PR #5090).

Question 9

What if no patch? (Workaround)

Accepted Answer

🚧 **No Patch Workaround**:
1. **Update Immediately**: Upgrade to v0.510.3+.
2. **WAF Rules**: Block requests containing `../` in file parameters.
3.…

Question 10

Is it urgent? (Priority Suggestion)

Accepted Answer

🔥 **Urgency**: **HIGH**.
⚡ **Priority**: **Critical**.
💡 **Reason**: Simple exploitation, high impact (data leak), and easy-to-find PoCs. Patch immediately to prevent unauthorized data access.

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

CVE-2023-35844 — 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