Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Eclipse Foundation | Eclipse BaSyx - Java Server SDK | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Eclipse | Basyx - Java Server Sdk |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.681% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Arbitrary File Write via Unauthenticated AAS Thumbnail Upload in Eclipse BaSyx Java Server SDK |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Arbitrary File Write via Unauthenticated AAS Thumbnail Upload in Eclipse BaSyx Java Server SDK |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Eclipse
Eclipse basyx - Java Server Sdk |
|
| Vendors & Products |
Eclipse
Eclipse basyx - Java Server Sdk |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Unauthenticated Arbitrary File Write via AAS Thumbnail API in Eclipse BaSyx Java Server SDK |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Unauthenticated Arbitrary File Write via AAS Thumbnail API in Eclipse BaSyx Java Server SDK |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Unauthenticated Arbitrary File Write via AAS Thumbnail Upload in Eclipse BaSyx Java Server SDK |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Unauthenticated Arbitrary File Write via AAS Thumbnail Upload in Eclipse BaSyx Java Server SDK |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In Eclipse BaSyx Java Server SDK versions 2.0.0-milestone-05 to 2.0.0-milestone-12, deployments using the MongoDB backend are vulnerable to an unauthenticated arbitrary file write through the AAS thumbnail API. The AAS thumbnail upload path accepted a client-controlled fileName request parameter and passed it through repository file handling as both a repository key and, during thumbnail retrieval, a local filesystem path. With the MongoDB file repository, the supplied filename was treated as an opaque GridFS key and was not normalized or restricted as a filesystem path. A remote attacker could upload thumbnail content using an absolute or traversal-style filename, then trigger thumbnail retrieval so that the uploaded bytes were written to the attacker-chosen path on the server filesystem. This could allow writing files anywhere the Java process has permission to write and may lead to remote code execution. The default InMemory backend is not affected by this specific path because it normalizes and restricts file paths to its temporary directory. The issue is fixed in Eclipse BaSyx Java Server SDK 2.0.0-milestone-13. | |
| Weaknesses | CWE-22 CWE-73 |
|
| References |
| |
| Metrics |
cvssV3_1
|