x/vulndb: potential Go vuln in github.com/sigstore/cosign: CVE-2023-46737

[GoVulnBot]

CVE-2023-46737 references github.com/sigstore/cosign, which may be a Go module.

Description:
Cosign is a sigstore signing tool for OCI containers. Cosign is susceptible to a denial of service by an attacker controlled registry. An attacker who controls a remote registry can return a high number of attestations and/or signatures to Cosign and cause Cosign to enter a long loop resulting in an endless data attack. The root cause is that Cosign loops through all attestations fetched from the remote registry in pkg/cosign.FetchAttestations. The attacker needs to compromise the registry or make a request to a registry they control. When doing so, the attacker must return a high number of attestations in the response to Cosign. The result will be that the attacker can cause Cosign to go into a long or infinite loop that will prevent other users from verifying their data. In Kyvernos case, an attacker whose privileges are limited to making requests to the cluster can make a request with an image reference to their own registry, trigger the infinite loop and deny other users from completing their admission requests. Alternatively, the attacker can obtain control of the registry used by an organization and return a high number of attestations instead the expected number of attestations. The issue can be mitigated rather simply by setting a limit to the limit of attestations that Cosign will loop through. The limit does not need to be high to be within the vast majority of use cases and still prevent the endless data attack. This issue has been patched in version 2.2.1 and users are advised to upgrade.

References:

• NIST: https://nvd.nist.gov/vuln/detail/CVE-2023-46737
• JSON: https://github.com/CVEProject/cvelist/tree/770fba269d409955480465ea6c4cee434f93ade6/2023/46xxx/CVE-2023-46737.json
• advisory: GHSA-vfp6-jrw2-99g9
• fix: sigstore/cosign@8ac891f
• Imported by: https://pkg.go.dev/github.com/sigstore/cosign?tab=importedby

Cross references:

• Module github.com/sigstore/cosign appears in issue x/vulndb: potential Go vuln in github.com/sigstore/cosign: CVE-2022-23649 #326 EFFECTIVELY_PRIVATE
• Module github.com/sigstore/cosign appears in issue x/vulndb: potential Go vuln in github.com/sigstore/cosign: CVE-2022-35929 #758 EFFECTIVELY_PRIVATE
• Module github.com/sigstore/cosign appears in issue x/vulndb: potential Go vuln in github.com/sigstore/cosign: CVE-2022-36056 #998 EFFECTIVELY_PRIVATE

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

modules:
    - module: github.com/sigstore/cosign
      vulnerable_at: 1.13.1
      packages:
        - package: cosign
cves:
    - CVE-2023-46737
references:
    - advisory: https://github.com/sigstore/cosign/security/advisories/GHSA-vfp6-jrw2-99g9
    - fix: https://github.com/sigstore/cosign/commit/8ac891ff0e29ddc67965423bee8f826219c6eb0f

[gopherbot]

Change https://go.dev/cl/540896 mentions this issue: data/reports: add GO-2023-2181.yaml