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**: ONEKEY Platform suffers from **Data Forgery** due to disabled mutual authentication. π **Consequences**: Remote attackers can execute **arbitrary commands** with elevated privileges on affected devices.
Q2Root Cause? (CWE/Flaw)
π‘οΈ **Root Cause**: **CWE-345** (Insufficient Verification of Data Authenticity). The core flaw is that **mutual authentication is disabled everywhere**, allowing untrusted data injection.
Q3Who is affected? (Versions/Components)
π’ **Affected**: **ONEKEY Platform** (specifically the **cph2_echarge_firmware** by vendor **hardy-barth**). These are **EV charging station controllers**.
Q4What can hackers do? (Privileges/Data)
π **Attacker Capabilities**: Remote, **unauthenticated** users can gain **elevated privileges**.β¦
π **Public Exploit**: **No**. The `pocs` list is empty. No public Proof-of-Concept or wild exploitation code is currently available in the provided data.
Q7How to self-check? (Features/Scanning)
π **Self-Check**: Scan for **ONEKEY Platform** components in EV charging infrastructure. Verify if **mutual authentication** is enabled on the `cph2_echarge_firmware`. Look for unauthorized command execution logs.
π§ **No Patch Workaround**: Since auth is disabled globally, **network segmentation** is critical. Isolate EV charging controllers from public networks. Restrict access to management interfaces strictly.
Q10Is it urgent? (Priority Suggestion)
π₯ **Urgency**: **HIGH**. CVSS Score is **Critical** (implied by H/H/H impacts). Although AC is High, the lack of auth requirement and potential for remote code execution makes immediate patching essential.