Affected by GO-2022-0390
and 6 other vulnerabilities
GO-2022-0390: Moby (Docker Engine) started with non-empty inheritable Linux process capabilities in github.com/docker/docker
GO-2022-0985: Docker supplementary group permissions not set up properly, allowing attackers to bypass primary group restrictions in github.com/docker/docker
GO-2022-1107: Container build can leak any path on the host into the container in github.com/docker/docker
GO-2023-1699: Docker Swarm encrypted overlay network may be unauthenticated in github.com/docker/docker
GO-2023-1700: Docker Swarm encrypted overlay network traffic may be unencrypted in github.com/docker/docker
GO-2023-1701: Docker Swarm encrypted overlay network with a single endpoint is unauthenticated in github.com/docker/docker
GO-2024-2914: Moby (Docker Engine) is vulnerable to Ambiguous OCI manifest parsing in github.com/docker/docker
Package etwlogs provides a log driver for forwarding container logs
as ETW events.(ETW stands for Event Tracing for Windows)
A client can then create an ETW listener to listen for events that are sent
by the ETW provider that we register, using the provider's GUID "a3693192-9ed6-46d2-a981-f8226c8363bd".
Here is an example of how to do this using the logman utility:
1. logman start -ets DockerContainerLogs -p {a3693192-9ed6-46d2-a981-f8226c8363bd} 0 0 -o trace.etl
2. Run container(s) and generate log messages
3. logman stop -ets DockerContainerLogs
4. You can then convert the etl log file to XML using: tracerpt -y trace.etl
Each container log message generates an ETW event that also contains:
the container name and ID, the timestamp, and the stream type.
Affected by 
Documentation
¶
Source Files