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.
CVSS Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:A/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
CVSS Score: 2.4
A local attacker regains access to a loopback-published service after an operator removes an automatically assigned port mapping and a later operation replays the retained publication request. Confidentiality impact depends on the listening service.
| Exploitability Metrics |
Vulnerable System Impact Metrics |
Subsequent System Impact Metrics |
| Attack Vector |
Local |
Confidentiality |
Low |
Confidentiality |
None |
| Attack Complexity |
Low |
Integrity |
None |
Integrity |
None |
| Attack Requirements |
None |
Availability |
None |
Availability |
None |
| Privileges Required |
Low |
| User Interaction |
Active |
A local attacker regains access to a loopback-published service after an operator removes an automatically assigned port mapping and a later operation replays the retained publication request. Confidentiality impact depends on the listening service.
CVSS 4.0
Publish services using an explicit host port instead of an automatically assigned port. Stop the listening service when withdrawing access until upgrading.
Upgrade Docker Sandboxes to version 0.53.0 or later.