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**: Low-privilege users can inject custom **Playwright code** in OneUptime < 10.0.20. π₯ **Consequence**: Leads to **Server-Side Remote Code Execution (RCE)**.β¦
π **Attacker Actions**: As a **low-privilege user**, you can execute arbitrary code on the server. π **Impact**: Full control (C:H, I:H, A:H). Can steal data, modify systems, or crash services.
Q5Is exploitation threshold high? (Auth/Config)
π **Threshold**: **Low**. Requires **PR:L** (Low Privileges). No UI interaction needed (UI:N). Network accessible (AV:N). Easy to exploit if you have a basic account.
Q6Is there a public Exp? (PoC/Wild Exploitation)
π΅οΈ **Public Exploit**: **No**. The `pocs` array is empty. No public PoC or wild exploitation code is currently available in the data.
Q7How to self-check? (Features/Scanning)
π **Self-Check**: Check your OneUptime version. If it is **< 10.0.20**, you are vulnerable. Look for features allowing **custom Playwright code** submission by low-privilege users.
Q8Is it fixed officially? (Patch/Mitigation)
β **Fixed**: **Yes**. Upgrade to **OneUptime 10.0.20** or later. π **Reference**: [GitHub Advisory GHSA-4j36-39gm-8vq8](https://github.com/OneUptime/oneuptime/security/advisories/GHSA-4j36-39gm-8vq8).
Q9What if no patch? (Workaround)
π§ **No Patch?**: Restrict access to Playwright features. Limit who can submit custom code. Apply network-level isolation. Monitor for unusual server processes.
Q10Is it urgent? (Priority Suggestion)
β‘ **Urgency**: **HIGH**. CVSS Score is **9.8** (Critical). RCE via low privileges is a severe threat. Patch immediately! πββοΈπ¨