Trust Boundary Violation due to Incomplete Blacklist in Test Failure Processing in Ares

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-23683: 0.36% estimated exploitation activity in the next 30 days; percentile 29.60 (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 allows an attacker to create special subclasses of InvocationTargetException that escape the exception sanitization because JUnit extracts the cause in a trusted context before the exception reaches Ares. This means that arbitrary student code can be executed in a trusted context, and that in turn allows disabling Ares and having full control over the system. Patches Update to version 1.7.6 or later. Workarounds Forbid student classes in trusted packages like, e.g., described in https://github.com/ls1intum/Ares/issues/15#issuecomment-996449371 References Are there any links users can visit to find out more? Not that I know of. For more information If you have any questions or comments about this advisory: Open an issue in https://github.com/ls1intum/Ares/issues Email us, see https://github.com/ls1intum/Ares/security/policy Detailed description Using generics, it is possible to throw checked exceptions without a throws clause: <details…

Published by the source

21 Jan 2022, 23:39 UTC

Last modified by the source

22 Jan 2026, 20:31 UTC

Source last checked

26 Oct 2026, 16:43 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-883x-6fch-6wjx

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

# Patch Next advisory brief: CVE-2024-23683

Advisory: Trust Boundary Violation due to Incomplete Blacklist in Test Failure Processing in Ares
IDs: CVE-2024-23683, GHSA-883x-6fch-6wjx
Record: https://patchnext.com/advisories/cve-2024-23683 (revision 1, source checked 26 Oct 2026, 16:43 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.7.6. A vendor fix does not mean a deployment is fixed.

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

## 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-883x-6fch-6wjx (GitHub-reviewed advisory GHSA-883x-6fch-6wjx lists affected ranges: Maven de.tum.in.ase:artemis-java-test-sandbox >=0 <1.7.6)

Commands are suggestions: review each one before running it.