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**: OpenClaw has a **Replay Attack** flaw during device pairing.…
🛡️ **Root Cause**: **CWE-294** (Capture and Replay). The system fails to validate the uniqueness/timestamp of the **bootstrap setup code** during the pairing handshake, allowing reuse.
Q3Who is affected? (Versions/Components)
📦 **Affected**: **OpenClaw** (Open-source AI Assistant). Specifically versions **before 2026.3.13**. If you are running an older build, you are vulnerable.
Q4What can hackers do? (Privileges/Data)
🔓 **Impact**: Full **Privilege Escalation**. Hackers can gain **operator.admin** rights. This means High Confidentiality, Integrity, and Availability impact (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
Q5Is exploitation threshold high? (Auth/Config)
⚡ **Threshold**: **LOW**. CVSS indicates **Network** accessible, **Low** complexity, **No** Privileges required, **No** User Interaction needed. It is an easy target for remote attackers.
Q6Is there a public Exp? (PoC/Wild Exploitation)
💣 **Public Exploit**: **No**. The `pocs` array is empty. No Proof-of-Concept code is currently available in the wild, but the logic is clear.
Q7How to self-check? (Features/Scanning)
🔍 **Self-Check**: Check your OpenClaw version. If it is **< 2026.3.13**, you are at risk. Monitor logs for repeated, identical **bootstrap setup codes** during pairing attempts.
Q8Is it fixed officially? (Patch/Mitigation)
✅ **Fix**: **Yes**. Patched in version **2026.3.13**. See GitHub Advisory **GHSA-63f5-hhc7-cx6p** and Commit **1803d16** for the official fix details.
Q9What if no patch? (Workaround)
🚧 **Workaround**: If you cannot patch immediately, **disable remote device pairing** or restrict network access to the pairing interface. Implement strict rate-limiting on bootstrap code submissions.
Q10Is it urgent? (Priority Suggestion)
🔥 **Urgency**: **CRITICAL**. Due to **No Auth** requirement and **Admin** escalation potential, patch immediately. Do not wait for an exploit to appear.