Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/vulndb: potential Go vuln in github.com/containerd/containerd: CVE-2023-25173 #1576

Closed
GoVulnBot opened this issue Feb 16, 2023 · 1 comment
Assignees

Comments

@GoVulnBot
Copy link

CVE-2023-25173 references github.com/containerd/containerd, which may be a Go module.

Description:
containerd is an open source container runtime. A bug was found in containerd prior to versions 1.6.18 and 1.5.18 where supplementary groups are not set up properly inside a container. If an attacker has direct access to a container and manipulates their supplementary group access, they may be able to use supplementary group access to bypass primary group restrictions in some cases, potentially gaining access to sensitive information or gaining the ability to execute code in that container. Downstream applications that use the containerd client library may be affected as well. This bug has been fixed in containerd v1.6.18 and v.1.5.18. Users should update to these versions and recreate containers to resolve this issue. Users who rely on a downstream application that uses containerd's client library should check that application for a separate advisory and instructions. As a workaround, ensure that the "USER $USERNAME" Dockerfile instruction is not used. Instead, set the container entrypoint to a value similar to ENTRYPOINT ["su", "-", "user"] to allow su to properly set up supplementary groups.

References:

Cross references:

See doc/triage.md for instructions on how to triage this report.

modules:
  - module: github.com/containerd/containerd
    packages:
      - package: containerd
description: |
    containerd is an open source container runtime. A bug was found in containerd prior to versions 1.6.18 and 1.5.18 where supplementary groups are not set up properly inside a container. If an attacker has direct access to a container and manipulates their supplementary group access, they may be able to use supplementary group access to bypass primary group restrictions in some cases, potentially gaining access to sensitive information or gaining the ability to execute code in that container. Downstream applications that use the containerd client library may be affected as well. This bug has been fixed in containerd v1.6.18 and v.1.5.18. Users should update to these versions and recreate containers to resolve this issue. Users who rely on a downstream application that uses containerd's client library should check that application for a separate advisory and instructions. As a workaround, ensure that the `"USER $USERNAME"` Dockerfile instruction is not used. Instead, set the container entrypoint to a value similar to `ENTRYPOINT ["su", "-", "user"]` to allow `su` to properly set up supplementary groups.
cves:
  - CVE-2023-25173
references:
  - web: https://www.benthamsgaze.org/2022/08/22/vulnerability-in-linux-containers-investigation-and-mitigation/
  - web: https://github.com/containerd/containerd/releases/tag/v1.5.18
  - web: https://github.com/containerd/containerd/releases/tag/v1.6.18
  - advisory: https://github.com/containerd/containerd/security/advisories/GHSA-hmfx-3pcx-653p
  - advisory: https://github.com/moby/moby/security/advisories/GHSA-rc4r-wh2q-q6c4
  - fix: https://github.com/containerd/containerd/commit/133f6bb6cd827ce35a5fb279c1ead12b9d21460a
  - advisory: https://github.com/advisories/GHSA-4wjj-jwc9-2x96
  - advisory: https://github.com/advisories/GHSA-fjm8-m7m6-2fjp
  - advisory: https://github.com/advisories/GHSA-phjr-8j92-w5v7

@timothy-king
Copy link
Contributor

Duplicate of #1574

@timothy-king timothy-king marked this as a duplicate of #1574 Feb 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants