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

Goal: 1000 CNY ยท Raised: 1359 CNY

100%

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!