Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2024-29021 is a critical-severity SSRF (CWE-918) vulnerability. Its CVSS base score is 9.0 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Default Accounts (T1078.001); ranked in the top 3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and CM-6 (Configuration Settings) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-26081
Vulnerability Data
Judge0 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…
more
unsandboxed code execution as root on the target machine. This vulnerability is fixed in 1.13.1.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.3.6V1.5.3V5.3.2V10.4.7
Mitigating Controls (NIST 800-53 r5) AI
Authenticator management requires verification of identity at initial distribution and secure handling that directly stops default passwords from remaining in use.
Information flow enforcement can restrict which destinations the server is allowed to contact on behalf of users.
Configuration settings establish the most restrictive secure baselines, which include changing or disabling default passwords.
Input validation directly stops untrusted URLs from being accepted and fetched without destination checks.
Boundary protection limits the network reach of server-initiated requests even if SSRF occurs.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Credential management directly requires replacing default passwords with unique, strong credentials.
Hardened configuration baselines explicitly prohibit default passwords, covering most of the weakness but not all identity-management aspects.
Secure development practices directly include input validation and destination allow-listing that prevent SSRF.
Runtime monitoring of web applications and services can detect anomalous outbound requests indicative of SSRF.
Vulnerability identification processes can discover and record SSRF flaws in web applications.
Authentication policies can enforce non-default passwords but do not address the full scope of credential lifecycle.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Mandates secure handling and change of authentication secrets, directly addressing default passwords.
Configuration management processes typically enforce changing defaults during hardening.
Operational threat data describing SSRF campaigns can be used to tighten outbound-request allow-lists and detection rules before attackers exploit them.
Requires secure authentication mechanisms, which includes replacing or disabling default credentials.
Utility programs often ship with defaults; control requires secure configuration before use.
Privileged accounts must not retain factory passwords, reducing risk of default-credential abuse.