CVE-2024-23682 — artemis-java-test-sandbox
HIGHCVE-2024-23682 is a high-severity (CVSS 8.2) CWE-501 vulnerability in de.tum.in.ase:artemis-java-test-sandbox. 2 public exploit references exist, so weaponization risk is real. A fix is available for de.tum.in.ase:artemis-java-test-sandbox — see the affected versions and patch details below.
Artemis Java Test Sandbox Class Loading Escape
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-23682.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2024-23682 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
de.tum.in.ase:artemis-java-test-sandboxReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Impact
This affects all Artemis users who test Java assignments. Ares is not required. Students code that gets automatically tested can run arbitrary code in the container, or arbitrary code on the machine of an assessor in case of manual correction.
Patches
The problem cannot be resolved easily in Ares itself. Use the Maven Enforcer Plugin as follows:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-enforcer-plugin</artifactId>
<version>3.0.0</version>
<executions>
<execution>
<id>enforce-no-student-code-in-trusted-packages</id>
<phase>process-classes</phase>
<goals>
<goal>enforce</goal>
</goals>
</execution>
</executions>
<configuration>
<rules>
<requireFilesDontExist>
<files>
<!-- ADD HERE THE RULES ARES TELLS YOU ARE MISSING -->
</files>
</requireFilesDontExist>
</rules>
</configuration>
</plugin>
This fails the build if student classes reside in such packages that Ares trusts. Trusted packages added in Ares using @AddTrustedPackage should be added as well.
For more information
If you have any questions or comments about this advisory:
- Open a discussion https://github.com/ls1intum/Ares/discussions
- Open an issue in https://github.com/ls1intum/Ares/issues
- Email us, see https://github.com/ls1intum/Ares/security/policy
References
See the assignment of Julius that passes the tests in TUM Artemis course: "Test - Praktikum: Grundlagen der Programmierung (Testkurs für Tutoren) - Security Tests" (if that still exists in 2022).
Also see #15 for almost the same problem.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | de.tum.in.ase:artemis-java-test-sandbox | all versions | 1.8.0de.tum.in.ase:artemis-java-test-sandbox:1.8.0 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for de.tum.in.ase:artemis-java-test-sandbox, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update de.tum.in.ase:artemis-java-test-sandbox to 1.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-23682 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-23682 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-23682. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-23682 in your dependencies?
O3 Security finds CVE-2024-23682 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.