Sigstore Cosign
Approved changes feed: RSS · Atom
cpe:2.3:a:sigstore:cosign:-:*:*:*:*:*:*:*
part: a version: - update: *
| Vendor | Sigstore (534c4401-0625-5be2-ae9b-f6c1539e71bc) |
|---|---|
| Product | Cosign (47b3b7a8-7deb-52a0-b40f-0f8d6514301d) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/rohankumardubey/cosign |
purl2cpe | 2026-06-01 10:15:40.674214 |
pkg:github/sigstore/cosign |
purl2cpe | 2026-06-01 10:15:40.674216 |
pkg:rpm/opensuse/cosign |
purl2cpe | 2026-06-01 10:15:40.674217 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-29903 |
vulnerable | 2026-06-08 06:33:29.518903 |
Cosign vulnerable to machine-wide denial of service via malicious artifacts
MEDIUM (4.2)
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.
Published: 2024-04-10T22:30:50.890Z
Updated: 2024-08-02T01:17:58.600Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.