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: GHSA-5j5w-g665-5m35 #360

Closed
GoVulnBot opened this issue Mar 24, 2022 · 5 comments
Assignees
Labels
excluded: EFFECTIVELY_PRIVATE This vulnerability exists in a package can be imported, but isn't meant to be outside that module.

Comments

@GoVulnBot
Copy link

In GitHub Security Advisory GHSA-5j5w-g665-5m35, there is a vulnerability in the following Go packages or modules:

Unit Fixed Vulnerable Ranges
github.com/containerd/containerd 1.5.8 >= 1.5.0, < 1.5.8

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

package: github.com/containerd/containerd
additional_packages:
  - package: github.com/containerd/containerd
    versions:
      - introduced: v0.0.0
        fixed: v1.4.12
versions:
  - introduced: v1.5.0
    fixed: v1.5.8
description: |-
    ### Impact

    In the OCI Distribution Specification version 1.0.0 and prior and in the OCI Image Specification version 1.0.1 and prior, manifest and index documents are ambiguous without an accompanying Content-Type HTTP header.  Versions of containerd prior to 1.4.12 and 1.5.8 treat the Content-Type header as trusted and deserialize the document according to that header.  If the Content-Type header changed between pulls of the same ambiguous document (with the same digest), the document may be interpreted differently, meaning that the digest alone is insufficient to unambiguously identify the content of the image.

    ### Patches

    This issue has been fixed in containerd 1.4.12 and 1.5.8.  Image pulls for manifests that contain a “manifests” field or indices which contain a “layers” field are rejected.

    ### Workarounds

    Ensure you only pull images from trusted sources.

    ### References

    https://github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m
    https://github.com/opencontainers/image-spec/security/advisories/GHSA-77vh-xpmg-72qh

    ### For more information
    If you have any questions or comments about this advisory:
    * Open an issue in [containerd](https://github.com/containerd/containerd/issues/new/choose)
    * Email us at [security@containerd.io](mailto:security@containerd.io)
published: 2021-11-18T16:08:58Z
last_modified: 2021-11-18T16:08:58Z
ghsas:
  - GHSA-5j5w-g665-5m35

@neild
Copy link
Contributor

neild commented Jul 13, 2022

Vulnerability in tool. Root cause vulnerability is #379.

@neild neild closed this as completed Jul 13, 2022
@tatianab tatianab added excluded: EFFECTIVELY_PRIVATE This vulnerability exists in a package can be imported, but isn't meant to be outside that module. and removed duplicate labels Jul 28, 2023
@tatianab
Copy link
Contributor

Needs excluded report

@tatianab tatianab reopened this Jul 28, 2023
@tatianab tatianab self-assigned this Jul 28, 2023
@gopherbot
Copy link
Contributor

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

@gopherbot
Copy link
Contributor

Change https://go.dev/cl/592767 mentions this issue: data/reports: unexclude 50 reports

@gopherbot
Copy link
Contributor

Change https://go.dev/cl/607216 mentions this issue: data/reports: unexclude 20 reports (14)

gopherbot pushed a commit that referenced this issue Aug 21, 2024
  - data/reports/GO-2022-0314.yaml
  - data/reports/GO-2022-0315.yaml
  - data/reports/GO-2022-0325.yaml
  - data/reports/GO-2022-0328.yaml
  - data/reports/GO-2022-0329.yaml
  - data/reports/GO-2022-0339.yaml
  - data/reports/GO-2022-0340.yaml
  - data/reports/GO-2022-0342.yaml
  - data/reports/GO-2022-0344.yaml
  - data/reports/GO-2022-0348.yaml
  - data/reports/GO-2022-0350.yaml
  - data/reports/GO-2022-0351.yaml
  - data/reports/GO-2022-0353.yaml
  - data/reports/GO-2022-0354.yaml
  - data/reports/GO-2022-0357.yaml
  - data/reports/GO-2022-0358.yaml
  - data/reports/GO-2022-0359.yaml
  - data/reports/GO-2022-0360.yaml
  - data/reports/GO-2022-0363.yaml
  - data/reports/GO-2022-0365.yaml

Updates #314
Updates #315
Updates #325
Updates #328
Updates #329
Updates #339
Updates #340
Updates #342
Updates #344
Updates #348
Updates #350
Updates #351
Updates #353
Updates #354
Updates #357
Updates #358
Updates #359
Updates #360
Updates #363
Updates #365

Change-Id: I88cff49c8c254ce8df68a3fb336657e69cb8ed58
Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/607216
Commit-Queue: Tatiana Bradley <tatianabradley@google.com>
Auto-Submit: Tatiana Bradley <tatianabradley@google.com>
Reviewed-by: Damien Neil <dneil@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
excluded: EFFECTIVELY_PRIVATE This vulnerability exists in a package can be imported, but isn't meant to be outside that module.
Projects
None yet
Development

No branches or pull requests

6 participants