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**: Tdarr (v2.00.15) suffers from **OS Command Injection** via the Help terminal. <br>๐ฅ **Consequences**: Attackers can execute **arbitrary commands** on the host system.โฆ
๐ **Privileges**: The injected commands run with the **privileges of the Tdarr process**. <br>๐ **Data**: Attackers can read/write files, exfiltrate sensitive data, or pivot to other internal systems.โฆ
๐ฃ **Public Exploit**: **YES**. <br>๐ **Source**: ExploitDB ID **50822** is available. <br>๐ฅ **Status**: Wild exploitation is possible since the PoC is public and requires no authentication.
Q7How to self-check? (Features/Scanning)
๐ **Self-Check**: <br>1. Verify your Tdarr version is **2.00.15**. <br>2. Check if the **Help terminal** is exposed to the internet. <br>3. Use scanners targeting **CWE-78** in web interfaces. <br>4.โฆ
๐ง **No Patch Workaround**: <br>1. **Block Access**: Restrict network access to the Help terminal port (Firewall rules). <br>2. **Disable**: If possible, disable the 'Help' feature or terminal access entirely. <br>3.โฆ
๐จ **Urgency**: **CRITICAL**. <br>โฑ๏ธ **Priority**: **Immediate Action Required**. <br>๐ **Reason**: Unauthenticated, remote, and public exploit exists. This is a 'zero-day' style risk for any exposed instance.โฆ