Artemis Java Test Sandbox versions up to 1.7.x trust boundary violation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Artemis Java Test Sandbox versions up to 1.7.x. This vulnerability affects unknown code. This manipulation causes trust boundary violation. This vulnerability is tracked as CVE-2024-23682. No exploit exists. You should upgrade the affected component.
Details
A vulnerability has been found in Artemis Java Test Sandbox versions up to 1.7.x (Programming Language Software) and classified as problematic. Affected by this vulnerability is some unknown functionality. The manipulation with an unknown input leads to a trust boundary violation vulnerability. The CWE definition for the vulnerability is CWE-501. The product mixes trusted and untrusted data in the same data structure or structured message. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Artemis Java Test Sandbox versions before 1.8.0 are vulnerable to a sandbox escape when an attacker includes class files in a package that Ares trusts. An attacker can abuse this issue to execute arbitrary Java when a victim executes the supposedly sandboxed code.
The weakness was disclosed 01/19/2024. The advisory is shared at github.com. This vulnerability is known as CVE-2024-23682 since 01/19/2024. Neither technical details nor an exploit are publicly available.
Upgrading to version 1.8.0 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2024-0368). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.7
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.2
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Trust boundary violationCWE: CWE-501
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Java Test Sandbox versions 1.8.0
Timeline
01/19/2024 🔍01/19/2024 🔍
01/19/2024 🔍
01/23/2026 🔍
Sources
Advisory: 15Status: Confirmed
CVE: CVE-2024-23682 (🔍)
GCVE (CVE): GCVE-0-2024-23682
GCVE (VulDB): GCVE-100-251617
EUVD: 🔍
Entry
Created: 01/19/2024 22:09Updated: 01/23/2026 12:35
Changes: 01/19/2024 22:09 (39), 02/15/2024 15:26 (2), 02/15/2024 15:31 (11), 11/28/2025 18:48 (16), 01/23/2026 12:35 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.