Cosign vulnerable to machine-wide denial of service via malicious artifacts
sigstore cosign
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/sigstore/cosign Go |
| No fix yet |
| github.com/sigstore/cosign/v2 Go |
|
|
sigstore cosign
| Product | Affected | Fixed in |
|---|---|---|
| github.com/sigstore/cosign Go |
| No fix yet |
| github.com/sigstore/cosign/v2 Go |
|
|
Cosign provides code signing and transparency for containers and binaries. Prior to version 2.2.4, maliciously-crafted software artifacts can cause denial of service of the machine running Cosign thereby impacting all services on the machine. The root cause is that Cosign creates slices based on the number of signatures, manifests or attestations in untrusted artifacts. As such, the untrusted artifact can control the amount of memory that Cosign allocates. The exact issue is Cosign allocates excessive memory on the lines that creates a slice of the same length as the manifests. Version 2.2.4 contains a patch for the vulnerability.
From the CVE record · GitHub_M
Cosign versions before 2.2.4 can allocate excessive memory when processing maliciously crafted software artifacts. This can cause a denial of service on the machine running Cosign and affect other services on that machine. The input does not specify whether authentication or user interaction is required.
Engineers using Go package github.com/sigstore/cosign/v2 before 2.2.4 or github.com/sigstore/cosign at any version should check their deployments.