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.

Sign up for GitHub

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

Jump to bottom

x/vulndb: potential Go vuln in github.com/containerd/containerd: CVE-2021-21334 #2321

Closed
tatianab opened this issue Nov 8, 2023 · 1 comment
Closed

x/vulndb: potential Go vuln in github.com/containerd/containerd: CVE-2021-21334 #2321

tatianab opened this issue Nov 8, 2023 · 1 comment
Labels
excluded: LEGACY_FALSE_POSITIVE (DO NOT USE) Vulnerability marked as false positive before we introduced the triage process

Comments

@tatianab
Copy link
Contributor

tatianab commented Nov 8, 2023

CVE-2021-21334 references github.com/containerd/containerd, which may be a Go module.

Description:
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 you are not launching multiple containers or Kubernetes pods from the same image which have different environment variables, you are not vulnerable to this issue. If you are not launching multiple containers or Kubernetes pods from the same image in rapid succession, you have reduced likelihood of being vulnerable to this issue This vulnerability has been fixed in containerd 1.3.10 and containerd 1.4.4. Users should update to these versions.

References:

Cross references:

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

modules:
    - module: github.com/containerd/containerd
      vulnerable_at: 1.7.8
      packages:
        - package: containerd
cves:
    - CVE-2021-21334
references:
    - advisory: https://github.com/containerd/containerd/security/advisories/GHSA-6g2q-w5j3-fwh4
    - web: https://github.com/containerd/containerd/releases/tag/v1.4.4
    - web: https://github.com/containerd/containerd/releases/tag/v1.3.10
    - fix: https://github.com/containerd/containerd/commit/05f951a3781f4f2c1911b05e61c160e9c30eaa8e
    - web: https://lists.fedoraproject.org/archives/list/[email protected]/message/KUE2Z2ZUWBHRU36ZGBD2YSJCYB6ELPXE/
    - web: https://lists.fedoraproject.org/archives/list/[email protected]/message/QIBPKSX5IOWPM3ZPFB3JVLXWDHSZTTWT/
    - web: https://lists.fedoraproject.org/archives/list/[email protected]/message/VTXHA5JOWQRCCUZH7ZQBEYN6KZKJEYSD/
    - web: https://security.gentoo.org/glsa/202105-33
@tatianab tatianab added the excluded: LEGACY_FALSE_POSITIVE (DO NOT USE) Vulnerability marked as false positive before we introduced the triage process label Nov 8, 2023
@gopherbot
Copy link
Contributor

Change https://go.dev/cl/540721 mentions this issue: data/excluded: batch add 135 excluded reports

@GoVulnBot GoVulnBot mentioned this issue Dec 19, 2023
Closed
@GoVulnBot GoVulnBot mentioned this issue Feb 1, 2024
Closed
@GoVulnBot GoVulnBot mentioned this issue May 14, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
excluded: LEGACY_FALSE_POSITIVE (DO NOT USE) Vulnerability marked as false positive before we introduced the triage process
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tatianab @gopherbot