CVE-2024-29902

What it is

Cosign provides code signing and transparency for containers and binaries. Prior to version 2.2.4, a remote image with a malicious attachment can cause denial of service of the host machine running Cosign. This can impact other services on the machine that rely on having memory available such as a Redis database which can result in data loss. It can also impact the availability of other services on the machine that will not be available for the duration of the machine denial. The root cause of this issue is that Cosign reads the attachment from a remote image entirely into memory without checking the size of the attachment first. As such, a large attachment can make Cosign read a large attachment into memory; If the attachments size is larger than the machine has memory available, the machine will be denied of service. The Go runtime will make a SigKill after a few seconds of system-wide denial. This issue can allow a supply-chain escalation from a compromised registry to the Cosign user: If an attacher has compromised a registry or the account of an image vendor, they can include a malicious attachment and hurt the image consumer. Version 2.2.4 contains a patch for the vulnerability.

At a glance

Exploitability

Can be exploited over the network with an admin-level account, but needs a user to act. High risk of service disruption.

Exploit odds

0.7% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2024-04-10 23:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 07:23 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.7% in the next 30 days (EPSS).
• Severity: 4.2 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2024-04-10 23:15 UTC

Last modified

2026-06-17 07:23 UTC

Exploit probability

0.7% · EPSS, next 30 days

Weakness

CWE-770 · Allocation without limits

Record status

Analyzed

Affected

• Sigstore Cosign < 2.2.4

Attack profile CVSS 3.1 · 4.2

Attack vector

Network

Complexity

High

Privileges needed

High

User interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2024-29902.md and follow it. Check whether this project is affected by CVE-2024-29902. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge