Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Datart | Datart | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-31012 | Datart 1.0.0-rc.3 is vulnerable to Directory Traversal. The configuration file handling of the application allows attackers to upload arbitrary YAML files to the config/jdbc-driver-ext.yml path. The application parses this file using SnakeYAML's unsafe load() or loadAs() method without input sanitization. This allows deserialization of attacker-controlled YAML content, leading to arbitrary class instantiation. Under certain conditions, this can be exploited to achieve remote code execution (RCE). |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.4% (1.351% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Running-elephant
Running-elephant datart |
|
| CPEs | cpe:2.3:a:running-elephant:datart:1.0.0:rc3:*:*:*:*:*:* | |
| Vendors & Products |
Running-elephant
Running-elephant datart |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Datart
Datart datart |
|
| Vendors & Products |
Datart
Datart datart |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-22 CWE-502 |
|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Datart 1.0.0-rc.3 is vulnerable to Directory Traversal. The configuration file handling of the application allows attackers to upload arbitrary YAML files to the config/jdbc-driver-ext.yml path. The application parses this file using SnakeYAML's unsafe load() or loadAs() method without input sanitization. This allows deserialization of attacker-controlled YAML content, leading to arbitrary class instantiation. Under certain conditions, this can be exploited to achieve remote code execution (RCE). | |
| References |
|