Jpom through 2.11.12 Cross-Workspace Authorization Bypass via Docker Controllers
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| dromara | Jpom | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Dromara | Jpom |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.373% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Dromara
Dromara jpom |
|
| Vendors & Products |
Dromara
Dromara jpom |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Jpom through 2.11.12 contains a cross-workspace authorization bypass vulnerability that allows authenticated users to manage other workspaces' Docker hosts by supplying foreign Docker asset ids. Attackers with Docker permission in any workspace can control containers, images, volumes and networks, including creating privileged containers with host bind mounts. | |
| Title | Jpom through 2.11.12 Cross-Workspace Authorization Bypass via Docker Controllers | |
| Weaknesses | CWE-639 | |
| References |
|
|
| Metrics |
cvssV3_1
|