Goal Reached Thanks to every supporter β€” we hit 100%!

Goal: 1000 CNY Β· Raised: 1000 CNY

100.0%

CVE-2024-28185 β€” AI Deep Analysis Summary

CVSS 10.0 Β· Critical

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.…

Q2Root Cause? (CWE/Flaw)

πŸ›‘οΈ **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).

Q5Is exploitation threshold high? (Auth/Config)

πŸ”“ **Threshold**: **LOW**! πŸ“‰ **Auth**: None required (PR:N). 🌐 **Network**: Remote (AV:N). 🧠 **Complexity**: Low (AC:L). πŸ™… **User Interaction**: None (UI:N). Super easy to exploit!

Q6Is there a public Exp? (PoC/Wild Exploitation)

πŸ•΅οΈ **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!