Class Loading Vulnerability in Artemis

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.2 · CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

EPSS

• CVE-2024-23682: 0.35% estimated exploitation activity in the next 30 days; percentile 28.65 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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: 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…

Published by the source

9 Feb 2022, 22:30 UTC

Last modified by the source

22 Jan 2026, 20:53 UTC

Source last checked

26 Oct 2026, 16:44 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-227w-wv4j-67h4

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-23682

Advisory: Class Loading Vulnerability in Artemis
IDs: CVE-2024-23682, GHSA-227w-wv4j-67h4
Record: https://patchnext.com/advisories/cve-2024-23682 (revision 1, source checked 26 Oct 2026, 16:44 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: de.tum.in.ase:artemis-java-test-sandbox 1.8.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven de.tum.in.ase:artemis-java-test-sandbox: affected < 1.8.0; fixed in 1.8.0

## Suggested inspection (read-only)
- Maven de.tum.in.ase:artemis-java-test-sandbox: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on de.tum.in.ase:artemis-java-test-sandbox.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-227w-wv4j-67h4 (GitHub-reviewed advisory GHSA-227w-wv4j-67h4 lists affected ranges: Maven de.tum.in.ase:artemis-java-test-sandbox >=0 <1.8.0)

Commands are suggestions: review each one before running it.