CVE-2024-28185 is a vulnerability in Judge0, an open-source online code execution system, where the application fails to properly account for symlinks within the sandbox directory. An attacker can pre-create a symlink at the path where Judge0 writes its 'run_script' file, causing the system to write to an arbitrary file outside the sandbox. This enables attackers to overwrite critical files or scripts on the host system, leading to code execution outside the intended sandbox environment.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module targeting the Judge0 online code execution platform (<= 1.13.0) for a sandbox escape vulnerability (CVE-2024-28185, CVE-2024-28189). The exploit abuses Judge0's improper handling of symlinks within the sandbox, allowing an attacker to write arbitrary files outside the sandbox and achieve code execution as root. The module interacts with the Judge0 HTTP API, enumerates available languages, and submits crafted code to create a malicious cron job in /etc/cron.d/. The payload is customizable and typically results in a reverse shell or arbitrary command execution. The exploit is weaponized, leveraging Metasploit's payload system, and is suitable for post-exploitation or red team operations against vulnerable Judge0 instances. The only file present is a Ruby Metasploit module, and all logic is contained within this file.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.