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**: Judge0 CE (v1.13.1-) fails to validate **symbolic links** inside its sandbox. ๐ **Consequences**: Attackers bypass isolation, writing arbitrary files & executing code **outside** the sandbox.โฆ
๐ก๏ธ **Root Cause**: **CWE-61** (Symbolic Link Following). The app ignores symlink safety checks. ๐ซ It trusts paths inside the sandbox without verifying if they point elsewhere. โ ๏ธ Critical logic flaw in `isolate_job.rb`.
Q3Who is affected? (Versions/Components)
๐ฏ **Affected**: **Judge0 CE** versions **before 1.13.1**. ๐ฆ Specifically the open-source online code execution system. ๐ข Vendor: **judge0**. Check your version immediately!
Q4What can hackers do? (Privileges/Data)
๐ **Attacker Power**: Full **Remote Code Execution (RCE)**! ๐ Can write arbitrary files anywhere on the host. ๐ Can execute malicious code outside the sandbox. ๐ **CVSS**: High (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H).
๐ต๏ธ **Public Exp?**: No specific PoC code listed in data. ๐ But **GitHub Advisory** (GHSA-h9g2-45c8-89cf) confirms the flaw. ๐ Source code links provided. Expect wild exploitation soon given low barrier!
Q7How to self-check? (Features/Scanning)
๐ **Self-Check**: 1. Check Judge0 version < 1.13.1. ๐ 2. Scan for exposed Judge0 CE instances. ๐ 3. Review `isolate_job.rb` logic if self-hosted. ๐ ๏ธ 4. Look for unexpected file writes outside sandbox.
Q8Is it fixed officially? (Patch/Mitigation)
โ **Fixed?**: **YES**! ๐ฉน Patch available in **v1.13.1+**. ๐ Commit `846d583` addresses the symlink issue. ๐ See GitHub advisory for details. Update NOW!
Q9What if no patch? (Workaround)
๐ง **No Patch?**: 1. **Isolate** the service strictly. ๐งฑ 2. Disable symlink creation in sandbox config. ๐ซ 3. Use strict file system permissions. ๐ 4. Monitor for anomalous file I/O. ๐
Q10Is it urgent? (Priority Suggestion)
๐ฅ **Urgency**: **CRITICAL**! ๐จ Remote, unauthenticated, low complexity. ๐ High impact (Confidentiality/Integrity/Availability). ๐โโ๏ธ Patch immediately to prevent RCE!