CVE-2024-29021
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJudge0 is an open-source online code execution system. The default configuration of Judge0 leaves the service vulnerable to a sandbox escape via Server Side Request Forgery (SSRF). This allows an attacker with sufficient access to the Judge0 API to obtain unsandboxed code execution as root on the target machine. This vulnerability is fixed in 1.13.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceJudge0's default configuration is vulnerable to Server Side Request Forgery (SSRF), which allows an attacker with sufficient API access to escape the sandbox and achieve unsandboxed code execution as root on the host machine.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Judge0 is installedCheck for Judge0 processes or search for judge0 directories (e.g., find / -name 'judge0*' 2>/dev/null, or ps aux | grep -i judge0)Affected if Judge0 is found running on the system
-
Determine the installed Judge0 versionCheck the version of the Judge0 installation. Common methods: check the Docker image tag if using containers (docker images), check a version file if installed from source, or query the API if accessible (GET /about or similar endpoint)Affected if The version is lower than 1.13.1 (e.g., 1.13.0 or earlier)
-
Verify if default configuration is in useExamine the Judge0 configuration files (typically config.yml, settings.yml, or environment variables). Look for default or unmodified settings, particularly related to network restrictions, sandbox settings, and allowed external requestsAffected if The configuration appears to be unchanged from defaults, especially network/sandbox settings
-
Check if the execution API is exposedDetermine if the /execute, /run, or similar code execution endpoints are accessible (check web server configuration, API firewall rules, or network access controls)Affected if The execution API is exposed without strong authentication or network-level restrictions
-
Inspect sandbox isolation settingsReview Judge0 sandbox configuration files or environment variables for settings controlling isolation (e.g., container runtime settings, seccomp profiles, or allow/deny rules for network requests)Affected if Sandbox isolation is not explicitly hardened or uses default permissive settings
A user is affected if they are running Judge0 version lower than 1.13.1 with default or unhardened configuration, where the execution API is accessible and sandbox isolation can be bypassed via SSRF.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Judge0 to version 1.13.1 or later and review/harden the default configuration to prevent SSRF-based sandbox escapes.
Upgrade to Judge0 version 1.13.1 or later
- Identify the current version of Judge0 currently deployed
- Back up all Judge0 data, configurations, and database
- Upgrade Judge0 to version 1.13.1 or later
- Verify the upgrade was successful by checking the version number
- Test that the sandbox escape vulnerability is no longer present by confirming SSRF protections are in place
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29021 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-29021 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data