ArcadeDB before 26.8.1 Per-Type ACL Bypass via Batch Handlers
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ArcadeData | arcadedb | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Arcadedata | Arcadedb |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.207% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Arcadedata
Arcadedata arcadedb |
|
| Vendors & Products |
Arcadedata
Arcadedata arcadedb |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | ArcadeDB before 26.8.1 fails to bind the authenticated principal (setCurrentUser) on its batch and time-series HTTP handlers. Because no principal is bound on the worker thread, the engine's fine-grained per-type ACL layer (LocalBucket.checkPermissionsOnFile) does not execute for these handlers. In deployments that use per-type or per-group ACLs, a user with database access but only limited per-type permissions can read from and write to types they are not authorized to access by submitting requests to the batch/time-series endpoints. Deployments that rely solely on database-level access control are not affected. | |
| Title | ArcadeDB before 26.8.1 Per-Type ACL Bypass via Batch Handlers | |
| Weaknesses | CWE-862 | |
| References |
| |
| Metrics |
cvssV3_1
|