Docker Engine TLS identity spoofing in SwarmKit Cluster-API proxy
moby SwarmKit · Docker Engine · Moby
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| moby SwarmKit |
| No fix yet |
| Docker Docker Engine |
| No fix yet |
| moby Moby |
| No fix yet |
| moby SwarmKit |
|
moby SwarmKit · Docker Engine · Moby
| Product | Affected | Fixed in |
|---|---|---|
| moby SwarmKit |
| No fix yet |
| Docker Docker Engine |
| No fix yet |
| moby Moby |
| No fix yet |
| moby SwarmKit |
|
| No fix yet |
SwarmKit's Cluster-API proxy can overwrite a forwarded client's TLS identity with an intermediary manager's identity. WithMetadataForwardTLSInfo replaces outgoing metadata with a copy of the incoming metadata, discarding the redirect guard's changes when built with grpc-go 1.39 or later. During a short window after a leader change, two proxy hops through managers with inconsistent views of the leader can allow an attacker possessing a valid worker node TLS certificate and private key to obtain a manager node certificate for the attacker's own key, escalating privileges from worker to manager. Applications built with an affected SwarmKit version and grpc-go 1.39 or later are impacted.
From the CVE record · Docker
SwarmKit's Cluster-API proxy can replace a forwarded client's TLS identity with an intermediary manager's identity when built with grpc-go 1.39 or later. During a short window after a leader change, an attacker with a valid worker node TLS certificate and private key can exploit two proxy hops through managers with inconsistent leader views to obtain a manager certificate for the attacker's own key.
Engineers running applications built with an affected SwarmKit version and grpc-go 1.39 or later should check their deployments.