docker-socket-proxy fails to properly gate read endpoints in the /containers Docker API namespace when the CONTAINERS environment variable is set. Attackers can use GET requests to /containers/{id}/archive, /containers/{id}/export, /containers/{id}/logs, and /containers/{id}/top to read arbitrary files and download entire container filesystems as tar archives.
Attack Parameters
Attack Vector
Adjacent
Requires local network access
Attack Complexity
Low
Easy to exploit
Attack Requirements
None
No additional conditions
Privileges Required
None
No privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
None
No data modification
Availability
None
No disruption
CVSS Vector v4.0
Weakness Type (CWE)
References 6
https://gist.github.com/nedlir/e4f52f88a757f02c67db1fd5dd70d732
disclosure@vulncheck.com
https://github.com/Tecnativa/docker-socket-proxy
disclosure@vulncheck.com
https://github.com/Tecnativa/docker-socket-proxy/blob/v0.5.0/haproxy.cfg#L49-L61
disclosure@vulncheck.com
https://github.com/Tecnativa/docker-socket-proxy/issues/182
disclosure@vulncheck.com
https://github.com/Tecnativa/docker-socket-proxy/pull/183
disclosure@vulncheck.com
https://www.vulncheck.com/advisories/docker-socket-proxy-through-insufficient-a…
disclosure@vulncheck.com