LiveActive security incident?Get immediate response
CVE Record

CVE-2024-23683: Artemis Java Test Sandbox InvocationTargetException Subclass Escape

Artemis Java Test Sandbox versions less than 1.7.6 are vulnerable to a sandbox escape when an attacker crafts a special subclass of InvocationTargetException. An attacker can abuse this issue to execute arbitrary Java when a victim executes the supposedly sandboxed code.

HighCVSS 8.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A vulnerable Java sandbox can be bypassed, allowing untrusted Java to run with capabilities expected to be blocked. The attacker must get specially crafted code executed by the victim system, such as a grading or testing workflow. This is serious where the sandbox protects servers from submitted code.

Executive priority

Patch promptly where this sandbox protects systems from user-submitted Java. Business urgency is high for education, assessment, CI, or testing services that rely on sandbox isolation. If the package is not deployed, priority is inventory confirmation rather than emergency response.

Technical view

Artemis Java Test Sandbox before 1.7.6 mishandles a crafted subclass of InvocationTargetException, enabling sandbox escape and arbitrary Java execution. The CVSS vector is local, low complexity, low privilege, user interaction required, changed scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to applications or platforms using de.tum.in.ase:artemis-java-test-sandbox versions before 1.7.6 to execute untrusted Java. Systems not using this package, or not running attacker-controlled Java through it, are unlikely to be affected based on the supplied sources.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation requires a victim system to execute the crafted Java inside the supposedly sandboxed environment; the attacker needs a path to submit or influence that code.

Researcher notes

The supplied affected metadata is sparse and includes an unusual versions value, but the description and advisories identify versions below 1.7.6 as vulnerable. Avoid assuming broader Artemis platform exposure without confirming this specific package and execution path.

Mitigation direction

  • Upgrade artemis-java-test-sandbox to version 1.7.6 or later.
  • Check the vendor advisory for any newer guidance before deployment.
  • Pause or restrict untrusted Java execution until vulnerable instances are patched.
  • Prioritize internet-accessible or multi-tenant grading and test execution systems.
  • Review dependency locks and build artifacts for older sandbox versions.

Validation and detection

  • Inventory Maven or Gradle dependencies for de.tum.in.ase:artemis-java-test-sandbox.
  • Confirm runtime artifacts resolve to version 1.7.6 or later.
  • Check whether user-submitted Java reaches this sandbox in production workflows.
  • Verify the 1.7.6 release or patch commit is included in deployed builds.
  • Run dependency scanning against the GitHub advisory identifier GHSA-883x-6fch-6wjx.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-653: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-23683 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.2 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.2CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H1.56CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

8.2High
CVSS 3.1 vector shape for CVE-2024-23683Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Unknown vendorde.tum.in.ase:artemis-java-test-sandboxde.tum.in.ase:artemis-java-test-sandbox, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.