Dokploy < 0.31.1 Broken Access Control via readAppMonitoring
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Dokploy | dokploy | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Dokploy | Dokploy |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.193% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Dokploy
Dokploy dokploy |
|
| Vendors & Products |
Dokploy
Dokploy dokploy |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Dokploy before 0.31.1 contains a missing ownership check vulnerability in the readAppMonitoring tRPC procedure that allows authenticated attackers to access container metrics belonging to other organizations by supplying an arbitrary appName. Attackers can query getApplicationStats with any application name, including the fixed "dokploy" control-plane service name, to read CPU, memory, network I/O, and block I/O metrics for containers they do not own on self-hosted multi-tenant instances. | |
| Title | Dokploy < 0.31.1 Broken Access Control via readAppMonitoring | |
| Weaknesses | CWE-639 | |
| References |
| |
| Metrics |
cvssV3_1
|