CVSS: 8.7EPSS: 0%CPEs: 2EXPL: 1CVE-2023-28840 – moby/moby's dockerd daemon encrypted overlay network may be unauthenticated
https://notcve.org/view.php?id=CVE-2023-28840
Moby is an open source container framework developed by Docker Inc. that is distributed as Docker, Mirantis Container Runtime, and various other downstream projects/products. The Moby daemon component (`dockerd`), which is developed as moby/moby, is commonly referred to as *Docker*. Swarm Mode, which is compiled in and delivered by default in dockerd and is thus present in most major Moby downstreams, is a simple, built-in container orchestrator that is implemented through a combination of SwarmKit and supporting network code. The overlay network driver is a core feature of Swarm Mode, providing isolated virtual LANs that allow communication between containers and services across the cluster. This driver is an implementation/user of VXLAN, which encapsulates link-layer (Ethernet) frames in UDP datagrams that tag the frame with a VXLAN Network ID (VNI) that identifies the originating overlay network. In addition, the overlay network driver supports an optional, off-by-default encrypted mode, which is especially useful when VXLAN packets traverses an untrusted network between nodes. Encrypted overlay networks function by encapsulating the VXLAN datagrams through the use of the IPsec Encapsulating Security Payload protocol in Transport mode. By deploying IPSec encapsulation, encrypted overlay networks gain the additional properties of source authentication through cryptographic proof, data integrity through check-summing, and confidentiality through encryption. When setting an endpoint up on an encrypted overlay network, Moby installs three iptables (Linux kernel firewall) rules that enforce both incoming and outgoing IPSec. • https://github.com/moby/libnetwork/security/advisories/GHSA-gvm4-2qqg-m333 https://github.com/moby/moby/issues/43382 https://github.com/moby/moby/pull/45118 https://github.com/moby/moby/security/advisories/GHSA-232p-vwff-86mp https://github.com/moby/moby/security/advisories/GHSA-33pg-m6jh-5237 https://github.com/moby/moby/security/advisories/GHSA-6wrf-mxfj-pf5p https://github.com/moby/moby/security/advisories/GHSA-vwm3-crmr-xfxw https://lists.fedoraproject.org/archives/list/packa • CWE-203: Observable Discrepancy CWE-420: Unprotected Alternate Channel CWE-636: Not Failing Securely ('Failing Open') CWE-755: Improper Handling of Exceptional Conditions •
CVSS: 6.8EPSS: 0%CPEs: 2EXPL: 1CVE-2023-28841 – moby/moby's dockerd daemon encrypted overlay network traffic may be unencrypted
https://notcve.org/view.php?id=CVE-2023-28841
Moby is an open source container framework developed by Docker Inc. that is distributed as Docker, Mirantis Container Runtime, and various other downstream projects/products. The Moby daemon component (`dockerd`), which is developed as moby/moby is commonly referred to as *Docker*. Swarm Mode, which is compiled in and delivered by default in `dockerd` and is thus present in most major Moby downstreams, is a simple, built-in container orchestrator that is implemented through a combination of SwarmKit and supporting network code. The `overlay` network driver is a core feature of Swarm Mode, providing isolated virtual LANs that allow communication between containers and services across the cluster. This driver is an implementation/user of VXLAN, which encapsulates link-layer (Ethernet) frames in UDP datagrams that tag the frame with the VXLAN metadata, including a VXLAN Network ID (VNI) that identifies the originating overlay network. In addition, the overlay network driver supports an optional, off-by-default encrypted mode, which is especially useful when VXLAN packets traverses an untrusted network between nodes. Encrypted overlay networks function by encapsulating the VXLAN datagrams through the use of the IPsec Encapsulating Security Payload protocol in Transport mode. By deploying IPSec encapsulation, encrypted overlay networks gain the additional properties of source authentication through cryptographic proof, data integrity through check-summing, and confidentiality through encryption. When setting an endpoint up on an encrypted overlay network, Moby installs three iptables (Linux kernel firewall) rules that enforce both incoming and outgoing IPSec. • https://github.com/moby/libnetwork/blob/d9fae4c73daf76c3b0f77e14b45b8bf612ba764d/drivers/overlay/encryption.go#L205-L207 https://github.com/moby/libnetwork/security/advisories/GHSA-gvm4-2qqg-m333 https://github.com/moby/moby/issues/43382 https://github.com/moby/moby/pull/45118 https://github.com/moby/moby/security/advisories/GHSA-232p-vwff-86mp https://github.com/moby/moby/security/advisories/GHSA-33pg-m6jh-5237 https://github.com/moby/moby/security/advisories/GHSA-6wrf-mxfj-pf5p https://gith • CWE-311: Missing Encryption of Sensitive Data CWE-636: Not Failing Securely ('Failing Open') CWE-755: Improper Handling of Exceptional Conditions •
CVSS: 6.8EPSS: 0%CPEs: 2EXPL: 0CVE-2023-28842 – moby/moby's dockerd daemon encrypted overlay network with a single endpoint is unauthenticated
https://notcve.org/view.php?id=CVE-2023-28842
Moby) is an open source container framework developed by Docker Inc. that is distributed as Docker, Mirantis Container Runtime, and various other downstream projects/products. The Moby daemon component (`dockerd`), which is developed as moby/moby is commonly referred to as *Docker*. Swarm Mode, which is compiled in and delivered by default in `dockerd` and is thus present in most major Moby downstreams, is a simple, built-in container orchestrator that is implemented through a combination of SwarmKit and supporting network code. The `overlay` network driver is a core feature of Swarm Mode, providing isolated virtual LANs that allow communication between containers and services across the cluster. This driver is an implementation/user of VXLAN, which encapsulates link-layer (Ethernet) frames in UDP datagrams that tag the frame with the VXLAN metadata, including a VXLAN Network ID (VNI) that identifies the originating overlay network. In addition, the overlay network driver supports an optional, off-by-default encrypted mode, which is especially useful when VXLAN packets traverses an untrusted network between nodes. Encrypted overlay networks function by encapsulating the VXLAN datagrams through the use of the IPsec Encapsulating Security Payload protocol in Transport mode. By deploying IPSec encapsulation, encrypted overlay networks gain the additional properties of source authentication through cryptographic proof, data integrity through check-summing, and confidentiality through encryption. When setting an endpoint up on an encrypted overlay network, Moby installs three iptables (Linux kernel firewall) rules that enforce both incoming and outgoing IPSec. • https://github.com/moby/libnetwork/security/advisories/GHSA-gvm4-2qqg-m333 https://github.com/moby/moby/security/advisories/GHSA-232p-vwff-86mp https://github.com/moby/moby/security/advisories/GHSA-33pg-m6jh-5237 https://github.com/moby/moby/security/advisories/GHSA-6wrf-mxfj-pf5p https://github.com/moby/moby/security/advisories/GHSA-vwm3-crmr-xfxw https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LYZOKMMVX4SIEHPJW3SJUQGMO5YZCPHC https://lists.fedoraproject.org/ • CWE-420: Unprotected Alternate Channel CWE-636: Not Failing Securely ('Failing Open') CWE-755: Improper Handling of Exceptional Conditions •
CVSS: 6.5EPSS: 0%CPEs: 1EXPL: 1CVE-2023-26054 – Credentials inlined to Git URLs could end up in provenance attestation in BuildKit
https://notcve.org/view.php?id=CVE-2023-26054
BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. In affected versions when the user sends a build request that contains a Git URL that contains credentials and the build creates a provenance attestation describing that build, these credentials could be visible from the provenance attestation. Git URL can be passed in two ways: 1) Invoking build directly from a URL with credentials. 2) If the client sends additional version control system (VCS) info hint parameters on builds from a local source. Usually, that would mean reading the origin URL from `.git/config` file. When a build is performed under specific conditions where credentials were passed to BuildKit they may be visible to everyone who has access to provenance attestation. • https://github.com/moby/buildkit/commit/75123c696506bdbca1ed69906479e200f1b62604 https://github.com/moby/buildkit/security/advisories/GHSA-gc89-7gcr-jxqc https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LYZOKMMVX4SIEHPJW3SJUQGMO5YZCPHC https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XNF4OLYZRQE75EB5TW5N42FSXHBXGWFE https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZTE4ITXXPIWZEQ4HYQCB6N6GZIMWXDAI https://access.redhat.com/securit • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •
CVSS: 7.1EPSS: 0%CPEs: 1EXPL: 2CVE-2021-32847 – Moby HyperKit uninitialized memory use in virtio-sock pci_vtsock_proc_tx
https://notcve.org/view.php?id=CVE-2021-32847
HyperKit is a toolkit for embedding hypervisor capabilities in an application. In versions 0.20210107 and prior, a malicious guest can trigger a vulnerability in the host by abusing the disk driver that may lead to the disclosure of the host memory into the virtualized guest. This issue is fixed in commit cf60095a4d8c3cb2e182a14415467afd356e982f. • https://github.com/moby/hyperkit/blob/2f061e447e1435cdf1b9eda364cea6414f2c606b/src/lib/pci_virtio_block.c#L316 https://github.com/moby/hyperkit/commit/cf60095a4d8c3cb2e182a14415467afd356e982f https://securitylab.github.com/advisories/GHSL-2021-058-moby-hyperkit • CWE-125: Out-of-bounds Read •