CVE-2021-40875 — AI Deep Analysis Summary

Q: Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: **Improper Access Control** (IAC). The `/files.md5` file on the client side is accessible without proper restrictions, leaking internal file structures.

Q: Who is affected? (Versions/Components)

📦 **Affected**: **Gurock Software Gurock TestRail**. 📅 **Versions**: All versions **before 7.2.0.3014**. 🌍 **Context**: Web-based QA/test case management software.

Q: What can hackers do? (Privileges/Data)

🕵️ **Attacker Actions**: 1. Access `/files.md5`. 2. Map application file paths. 3. Probe specific paths. 4. **Steal**: Hardcoded passwords, API keys, sensitive config data.

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

⚡ **Exploitation Threshold**: **LOW**. 🔓 **Auth**: No authentication required to access the `/files.md5` endpoint. ⚙️ **Config**: Default installation behavior allows this exposure.

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

🔍 **Self-Check**: 1. Visit `http://<target>/files.md5`. 2. If you see a list of files/paths, you are **VULNERABLE**. 3. Use automated scanners like Nuclei or the Python scripts linked in the data.

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

🩹 **Official Fix**: **YES**. ✅ **Patch**: Upgrade to version **7.2.0.3014** or later. 📢 **Status**: Fixed by Gurock Software.

Q: Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **HIGH**. ⚠️ **Reason**: Easy to exploit, no auth needed, leads to credential/API key leaks. 🚀 **Action**: Patch immediately or block endpoint via WAF/Config.

Updated May 08, 2026

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**: Improper Access Control in Gurock TestRail. <br>💥 **Consequences**: Attackers access `/files.md5` to get a full list of app files & paths.…

Read full answer (login)

Q2Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: **Improper Access Control** (IAC). The `/files.md5` file on the client side is accessible without proper restrictions, leaking internal file structures.

Q3Who is affected? (Versions/Components)

📦 **Affected**: **Gurock Software Gurock TestRail**. <br>📅 **Versions**: All versions **before 7.2.0.3014**. <br>🌍 **Context**: Web-based QA/test case management software.

Q4What can hackers do? (Privileges/Data)

🕵️ **Attacker Actions**: <br>1. Access `/files.md5`. <br>2. Map application file paths. <br>3. Probe specific paths. <br>4. **Steal**: Hardcoded passwords, API keys, sensitive config data.

Q5Is exploitation threshold high? (Auth/Config)

⚡ **Exploitation Threshold**: **LOW**. <br>🔓 **Auth**: No authentication required to access the `/files.md5` endpoint. <br>⚙️ **Config**: Default installation behavior allows this exposure.

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

💣 **Public Exp/PoC**: **YES**. <br>🔗 Tools available: <br>- `derailed` (SakuraSamuraii) <br>- `TestRail-files.md5-IAC-scanner` (Lul) <br>- Nuclei templates (ProjectDiscovery).…

Read full answer (login)

Q7How to self-check? (Features/Scanning)

🔍 **Self-Check**: <br>1. Visit `http://<target>/files.md5`. <br>2. If you see a list of files/paths, you are **VULNERABLE**. <br>3. Use automated scanners like Nuclei or the Python scripts linked in the data.

Q8Is it fixed officially? (Patch/Mitigation)

🩹 **Official Fix**: **YES**. <br>✅ **Patch**: Upgrade to version **7.2.0.3014** or later. <br>📢 **Status**: Fixed by Gurock Software.

Q9What if no patch? (Workaround)

🚧 **No Patch Workaround**: <br>1. **Block Access**: Configure Web Server (Nginx/Apache) to deny requests to `/files.md5`. <br>2. **WAF Rules**: Add rule to block access to this specific endpoint. <br>3.…

Read full answer (login)

Q10Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **HIGH**. <br>⚠️ **Reason**: Easy to exploit, no auth needed, leads to credential/API key leaks. <br>🚀 **Action**: Patch immediately or block endpoint via WAF/Config.

Continue exploring

Vulnerability detail Full AI analysis (login) n/a