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**: NocoDB suffers from a **Path Traversal** vulnerability. ๐ ๐ฅ **Consequences**: Attackers can read **arbitrary files** on the server. This includes sensitive configs, source code, and private data. ๐ฑ
Q2Root Cause? (CWE/Flaw)
๐ก๏ธ **Root Cause**: **Path Traversal** flaw in the `/download` route. ๐ โ ๏ธ **Flaw**: The `path` parameter is not properly sanitized. ๐ซ ๐ **CWE**: Not explicitly listed, but classic **Directory Traversal** (CWE-22).
๐ **Hackers Can**: Access **ANY file** on the server. ๐ ๐ **Privileges**: Unauthenticated access. ๐ช ๐ฆ **Data Risk**: Config files, source code, secrets, and sensitive info. ๐คซ
Q5Is exploitation threshold high? (Auth/Config)
๐ **Threshold**: **LOW**. ๐ ๐ **Auth**: **Unauthenticated**. No login needed! ๐ซ โ๏ธ **Config**: Just manipulate the `path` parameter in the `/download` route. ๐ฎ
Q6Is there a public Exp? (PoC/Wild Exploitation)
๐ฅ **Public Exp?**: **YES**. โ ๐ **PoCs**: Available on GitHub (e.g., Lserein, b3nguang). ๐ป ๐ค **Automated**: Nuclei templates exist for scanning. ๐ ๐ **Wild Exp**: High risk of automated exploitation. โก
Q7How to self-check? (Features/Scanning)
๐ **Self-Check**: Scan for NocoDB instances. ๐ต๏ธโโ๏ธ ๐งช **Test**: Send request to `/download` with `path=../../etc/passwd`. ๐ ๐ก **Tools**: Use Nuclei or custom scripts to detect the flaw. ๐ ๏ธ
Q8Is it fixed officially? (Patch/Mitigation)
๐ ๏ธ **Fixed?**: Yes, for versions **> 0.106.1**. โ ๐ฆ **Patch**: Update NocoDB to the latest version. ๐ ๐ **Ref**: See GitHub commits for the fix in `attachment.ctl.ts`. ๐
Q9What if no patch? (Workaround)
๐ง **No Patch?**: **Mitigate**. ๐ก๏ธ ๐ซ **Block**: Restrict access to `/download` route via WAF. ๐งฑ ๐ **Auth**: Force authentication if possible. ๐ ๐ **Limit**: Disable file download features if not needed. ๐
Q10Is it urgent? (Priority Suggestion)
โก **Urgency**: **HIGH**. ๐ด ๐จ **Priority**: Patch immediately! ๐โโ๏ธ ๐ข **Reason**: Unauthenticated, easy exploit, sensitive data at risk. ๐ฑ ๐ **Published**: June 2023, but still relevant for unpatched systems. ๐