p PatchFirst

PatchFirst · Latest vulnerabilities

containerd vulnerabilities · Page 2

Vulnerabilities published for containerd in the last 30 days: 3. Listed in the KEV catalogue: 0.

RSS ↗
Filter vulnerabilities
Clear filters

Vulnerabilities: 23

  1. CVE-2021-21334

    Medium · CVSS 6.3EPSS 1.95%Fix available

    environment variable leak

    In containerd (an industry-standard container runtime) before versions 1.3.10 and 1.4.4, containers launched through containerd's CRI implementation (through Kubernetes, crictl, or any other pod/container client that uses the containerd CRI service) that share the same image may receive incorrect environment variables, including values that are defined for other containers. If the affected containers have different security contexts, this may allow sensitive information to be unintentionally shared. If you are not using containerd's CRI implementation (through one of the mechanisms described above), you are not vulnerable to this issue. If yo

    • Update to 1.4.4~ds1-1
    Published Updated
  2. CVE-2020-15257

    Medium · CVSS 5.2EPSS 3.24%Fix available

    containerd-shim API Exposed to Host Network Containers

    containerd is an industry-standard container runtime and is available as a daemon for Linux and Windows. In containerd before versions 1.3.9 and 1.4.3, the containerd-shim API is improperly exposed to host network containers. Access controls for the shim’s API socket verified that the connecting process had an effective UID of 0, but did not otherwise restrict access to the abstract Unix domain socket. This would allow malicious containers running in the same network namespace as the shim, with an effective UID of 0 but otherwise reduced privileges, to cause new processes to be run with elevated privileges. This vulnerability has been fixed i

    • Update to 1.4.3~ds1-1
    Published Updated
  3. CVE-2020-15157

    Medium · CVSS 6.1EPSS 2.3%Fix available

    containerd can be coerced into leaking credentials during image pull

    In containerd (an industry-standard container runtime) before version 1.2.14 there is a credential leaking vulnerability. If a container image manifest in the OCI Image format or Docker Image V2 Schema 2 format includes a URL for the location of a specific image layer (otherwise known as a “foreign layer”), the default containerd resolver will follow that URL to attempt to download it. In v1.2.x but not 1.3.0 or later, the default containerd resolver will provide its authentication credentials if the server where the URL is located presents an HTTP 401 status code along with registry-specific HTTP headers. If an attacker publishes a public im

    • Update to 1.3.2~ds1-2
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →