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**: Remote Code Execution (RCE) in ZeroShell's `cgi-bin/kerbynet`. π **Consequences**: Attackers can execute arbitrary system commands, leading to total system compromise.
Q2Root Cause? (CWE/Flaw)
π‘οΈ **Root Cause**: Improper neutralization of special elements used in an OS command (Injection). π₯ **Flaw**: Shell metacharacters in the `type` parameter of `NoAuthREQ x509List` are not sanitized.
Q3Who is affected? (Versions/Components)
π¦ **Affected**: ZeroShell 1.0beta11 and earlier versions. π₯οΈ **Component**: The `cgi-bin/kerbynet` CGI script.
Q4What can hackers do? (Privileges/Data)
π **Privileges**: Arbitrary commands execution. π **Data**: Full control over the embedded Linux server, potentially exposing network configs, firewall rules, and sensitive data.
Q5Is exploitation threshold high? (Auth/Config)
π **Threshold**: LOW. π **Auth**: No authentication required (`NoAuthREQ`). Remote attackers can exploit this directly over the network.
Q6Is there a public Exp? (PoC/Wild Exploitation)
π£ **Exploit**: YES. Public PoC available on Exploit-DB (ID: 8023) and Nuclei templates. π **Status**: Wild exploitation is possible.
Q7How to self-check? (Features/Scanning)
π **Check**: Scan for `cgi-bin/kerbynet` endpoint. π§ͺ **Test**: Inject shell metacharacters into the `type` parameter of `NoAuthREQ x509List` action.
π§ **Workaround**: If patching is impossible, restrict network access to `cgi-bin/kerbynet` via firewall rules. π« **Block**: Prevent external access to this specific CGI path.
Q10Is it urgent? (Priority Suggestion)
π₯ **Priority**: CRITICAL. π¨ **Urgency**: High. Since it requires no auth and allows RCE, it is an immediate threat to any exposed ZeroShell instance.