Docker Sandboxes restores removed automatically assigned port publications
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Docker | Docker Sandboxes | unknown |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Docker | Docker Sandboxes |
|
Vendor Solution
Upgrade Docker Sandboxes to version 0.53.0 or later.
Vendor Workaround
Publish services using an explicit host port instead of an automatically assigned port. Stop the listening service when withdrawing access until upgrading.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Link | Providers |
|---|---|
| https://docs.docker.com/ai/sandboxes/ |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Docker
Docker docker Sandboxes |
|
| Vendors & Products |
Docker
Docker docker Sandboxes |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Docker Sandboxes can silently republish a sandbox service after an operator removes its automatically assigned host-port mapping. The daemon removes the active binding but retains the original publication request, allowing a later port change or sandbox restart to publish the service again on a new host port. An attacker able to reach the restored endpoint may regain access to the service. Both TCP and UDP mappings are affected. Exposure is limited to the original bind address, which defaults to loopback. The issue is fixed in version 0.53.0. | |
| Title | Docker Sandboxes restores removed automatically assigned port publications | |
| Weaknesses | CWE-672 | |
| References |
| |
| Metrics |
cvssV4_0
|