Security readout for executives and security teams
Plain-English summary
This flaw weakens a Java sandbox used to run test code. A malicious low-privileged user could package classes in a trusted location so that a victim runs code believed to be sandboxed, but arbitrary Java executes instead.
Executive priority
Prioritize remediation where the sandbox protects production, shared, or educational code-execution infrastructure. The issue is high impact, but supplied evidence does not indicate internet-remote exploitation or known active abuse.
Technical view
Artemis Java Test Sandbox before 1.8.0 has a class-loading sandbox escape involving packages trusted by Ares. The CVSS vector indicates local attack, low complexity, low privileges, required user interaction, changed scope, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely in systems using de.tum.in.ase:artemis-java-test-sandbox before 1.8.0 to execute untrusted or semi-trusted Java submissions, such as automated testing or educational code-evaluation workflows.
Exploitation context
The supplied sources do not show CISA KEV listing or active exploitation. Exploitation requires a victim to execute supposedly sandboxed code containing attacker-controlled class files in a trusted package context.
Researcher notes
Key uncertainty is the exact affected version range beyond “before 1.8.0” and package metadata showing version 0. Treat vendor advisories and the 1.8.0 release as the primary remediation evidence.
Mitigation direction
- Upgrade artemis-java-test-sandbox to version 1.8.0 or later.
- Review the Ares and GitHub advisory pages for vendor guidance.
- Temporarily avoid executing untrusted Java submissions on vulnerable sandbox versions.
- Run untrusted code only inside separately hardened infrastructure until upgraded.
Validation and detection
- Inventory dependency manifests for de.tum.in.ase:artemis-java-test-sandbox.
- Confirm deployed runtime artifacts are version 1.8.0 or later.
- Identify workflows that execute user-submitted Java through Ares or Artemis sandboxing.
- Review sandbox execution logs for unexpected Java behavior around untrusted submissions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-501: 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 lookupCWE-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 lookupPrivilege 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 lookupCVE-2024-23682 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H1.56CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/ls1intum/Ares/security/advisories/GHSA-227w-wv4j-67h4CVE reference, VulnCheck · vendor-advisory
- https://github.com/ls1intum/Ares/issues/15CVE reference, VulnCheck · issue-tracking
- https://github.com/ls1intum/Ares/releases/tag/1.8.0CVE reference, VulnCheck · related
- https://github.com/advisories/GHSA-227w-wv4j-67h4CVE reference, VulnCheck · vendor-advisory
- https://vulncheck.com/advisories/vc-advisory-GHSA-227w-wv4j-67h4CVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.