Vulnerability in de.tum.in.ase:artemis-java-test-sandbox (CVE-2024-23682)
Summary
Vulnerability in de.tum.in.ase:artemis-java-test-sandbox (CVE-2024-23682). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.8.0 or later.
Original description
The description as published by the source.
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:
org.apache.maven.plugins
maven-enforcer-plugin
3.0.0
enforce-no-student-code-in-trusted-packages
process-classes
enforce
<!-- ADD HERE THE RULES ARES TELLS YOU ARE MISSING -->
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2024-23682 has been found in de.tum.in.ase:artemis-java-test-sandbox.
Successful exploitation can lead to full system takeover. CVSS score: 8.2/10.
What to do: upgrade de.tum.in.ase:artemis-java-test-sandbox to 1.8.0 or later.
If unsure, ask your IT team or search "de.tum.in.ase:artemis-java-test-sandbox CVE-2024-23682" on the vendor's site.
CVE-2024-23682 (de.tum.in.ase:artemis-java-test-sandbox) — CWE-501 / CVSS v3 8.2
Attack vector: local
Patched: 1.8.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-501) exists in de.tum.in.ase:artemis-java-test-sandbox.
Check the vendor advisory for the affected versions of de.tum.in.ase:artemis-java-test-sandbox.
Severity: High (CVSS 8.2/10). Successful exploitation can lead to full system takeover.
Update to 1.8.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで de.tum.in.ase:artemis-java-test-sandbox を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade de.tum.in.ase:artemis-java-test-sandbox to 1.8.0ステージング環境で 1.8.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- exploit github.com
- package github.com
- web github.com
- web github.com
- web github.com
- web vulncheck.com