Vulnerabilidades de Docker

Docker

The firewall rules which mark VXLAN datagrams for encryption indiscriminately match both authentic VXLAN datagrams sent from the kernel and forged datagrams sent by user processes. Any packet sent…

Sin parche todavía.

Docker

Docker Engine classifies a registry hostname as insecure using an any-match DNS check. loadInsecureRegistries() injects 127.0.0.0/8 and ::1/128 as insecure CIDRs by default. isCIDRMatch resolves all…

Sin parche todavía.

Docker

When proxy networking with CA injection is enabled, a build can modify its CA bundle before cleanup. This may cause cleanup to block, operate outside the build rootfs, or fail without failing the…

Sin parche todavía.

Docker

If BuildKit daemon is started with --cdi-disabled it can lead to daemon panic when builds try to use CDI devices. This can happen maliciously or by accident.

Sin parche todavía.

Docker

An unauthenticated attacker controlling a registry or OCI-layout blob source could provide blob contents that did not match the claimed digest. The resulting snapshot could be cached under that…

Sin parche todavía.

Docker

A malicious image can advertise DiffIDs from another image while containing different layer contents. In affected versions, BuildKit could use the advertised DiffIDs to derive cache and snapshot…

Sin parche todavía.

Docker

A malicious external BuildKit frontend can send requests using the internal API that can create conditions for a data race that can cause the BuildKit daemon to panic.

Sin parche todavía.

Docker

BuildKit may be tricked into performing file actions with special file inodes where regular files are expected. Special files may block operations or, on rootful workers, allow unintended host device…

Sin parche todavía.

Docker

A malicious frontend can submit an LLB definition that causes buildkitd to panic and terminate, interrupting all builds running on that daemon.

Sin parche todavía.

Docker

A malicious frontend can submit an LLB definition that causes buildkitd to panic and terminate, interrupting all builds running on that daemon.

Sin parche todavía.

Docker

The Dockerfile frontend loaded the Dockerfile and .dockerignore files of a build context into memory without a size limit. A build context containing an oversized file could make buildkitd allocate…

Sin parche todavía.

Docker

A build step for a Git source, crafted in a specific way, can bypass some policy validation rules. A malicious build definition can make the repository look like it is coming from a different remote…

Sin parche todavía.

Docker

The guest-to-host Unix-domain socket relay in Docker Sandboxes validates that a socket path is inside an authorized workspace, but later reconnects using the pathname. A malicious guest can replace…

Sin parche todavía.

Docker

The tar extraction routines in moby/go-archive (Unpack, UnpackLayer, Untar/UntarUncompressed, and the ApplyLayer helpers) do not confine filesystem operations to the destination directory. The…

Sin parche todavía.

Docker

Un mensaje manipulado en la API de compilación de bajo nivel de BuildKit puede usarse para eliminar el contenido del directorio /tmp. La acción que normalmente se puede usar para eliminar archivos…

Sin parche todavía.

Docker

Un cliente o frontend malicioso de BuildKit podría crear una solicitud que podría provocar que el daemon de BuildKit se bloquee con un panic.

Sin parche todavía.

Docker

Los frontends o clientes personalizados de BuildKit que usan la API de bajo nivel sin procesar pueden establecer git.checkoutbundle=true al hacer checkout de fuentes Git. Si la fuente Git es…

Sin parche todavía.