<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 04:07:55 +0000</lastBuildDate>
    <item>
      <title>BIT-cosign-2024-29903 — Cosign vulnerable to machine-wide denial of service via malicious artifacts</title>
      <link>https://cve.radiocsirt.org/vuln/bit-cosign-2024-29903</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: cosign&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: cosign&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-cosign-2024-29903</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0622 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Certaines d'entre elles permettent à un attaq…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0622</link>
      <description>certfr-2025-avi-0622</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0622</guid>
    </item>
    <item>
      <title>EUVD-2026-4695</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-4695</link>
      <description>EUVD-2026-4695</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-4695</guid>
    </item>
    <item>
      <title>fkie_cve-2024-29903</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-29903</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-29903</guid>
    </item>
    <item>
      <title>GHSA-95pr-fxf5-86gv — Cosign malicious artifacts can cause machine-wide DoS</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-95pr-fxf5-86gv</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/sigstore/cosign, Go: github.com/sigstore/cosign/v2&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;As an example, these lines demonstrate the problem:&lt;/p&gt;
&lt;p&gt;https://github.com/sigstore/cosign/blob/286a98a4a99c1b2f32f84b0d560e324100312280/pkg/oci/remote/signatures.go#L56-L70&lt;/p&gt;
&lt;p&gt;This `Get()` method gets the manifest of the image, allocates a slice equal to the length of the layers in the manifest, loops through the layers and adds a new signature to the slice.&lt;/p&gt;
&lt;p&gt;The exact issue is Cosign allocates excessive memory on the lines that creates a slice of the same length as the manifests.&lt;/p&gt;
&lt;p&gt;## Remediation&lt;/p&gt;
&lt;p&gt;Update to the latest version of Cosign, where the number of attestations, signatures and manifests has been limited to a reasonable value.&lt;/p&gt;
&lt;p&gt;## Cosign PoC&lt;/p&gt;
&lt;p&gt;In the case of this API (also referenced above):&lt;/p&gt;
&lt;p&gt;https://github.com/sigstore/cosign/blob/286a98a4a99c1b2f32f84b0d560e324100312280/pkg/oci/remote/signatures.go#L56-L70&lt;/p&gt;
&lt;p&gt;… The first line can contain a length that is safe for the system and will not throw a runtime panic or be blocked by other safety mechanisms. For the sake of argument, let’s say that the length of `m, err := s.Manifest()` is the max allowed (by the machine without throwing OOM panics) manifests minus 1. Wh…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/sigstore/cosign, Go: github.com/sigstore/cosign/v2&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;As an example, these lines demonstrate the problem:&lt;/p&gt;
&lt;p&gt;https://github.com/sigstore/cosign/blob/286a98a4a99c1b2f32f84b0d560e324100312280/pkg/oci/remote/signatures.go#L56-L70&lt;/p&gt;
&lt;p&gt;This `Get()` method gets the manifest of the image, allocates a slice equal to the length of the layers in the manifest, loops through the layers and adds a new signature to the slice.&lt;/p&gt;
&lt;p&gt;The exact issue is Cosign allocates excessive memory on the lines that creates a slice of the same length as the manifests.&lt;/p&gt;
&lt;p&gt;## Remediation&lt;/p&gt;
&lt;p&gt;Update to the latest version of Cosign, where the number of attestations, signatures and manifests has been limited to a reasonable value.&lt;/p&gt;
&lt;p&gt;## Cosign PoC&lt;/p&gt;
&lt;p&gt;In the case of this API (also referenced above):&lt;/p&gt;
&lt;p&gt;https://github.com/sigstore/cosign/blob/286a98a4a99c1b2f32f84b0d560e324100312280/pkg/oci/remote/signatures.go#L56-L70&lt;/p&gt;
&lt;p&gt;… The first line can contain a length that is safe for the system and will not throw a runtime panic or be blocked by other safety mechanisms. For the sake of argument, let’s say that the length of `m, err := s.Manifest()` is the max allowed (by the machine without throwing OOM panics) manifests minus 1. Wh…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-95pr-fxf5-86gv</guid>
    </item>
    <item>
      <title>gsd-2024-29903</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-29903</link>
      <description>gsd-2024-29903</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-29903</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:13863-1 — cosign-2.2.4-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:13863-1</link>
      <description>&lt;p&gt;cosign-2.2.4-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;cosign-2.2.4-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:13863-1</guid>
    </item>
    <item>
      <title>RHEA-2024:4022 — Red Hat Enhancement Advisory: Red Hat OpenShift Pipelines Client tkn for 1.15.0 release</title>
      <link>https://cve.radiocsirt.org/vuln/rhea-2024:4022</link>
      <description>&lt;p&gt;golang: net/http, x/net/http2: unlimited number of CONTINUATION frames causes DoS cloudevents/sdk-go: usage of WithRoundTripper to create a Client leaks credentials jose-go: improper handling of highly compressed data cosign: Malicious attachments can cause system-wide denial of service cosign: Malicious artifects can cause machine-wide denial of service&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;golang: net/http, x/net/http2: unlimited number of CONTINUATION frames causes DoS cloudevents/sdk-go: usage of WithRoundTripper to create a Client leaks credentials jose-go: improper handling of highly compressed data cosign: Malicious attachments can cause system-wide denial of service cosign: Malicious artifects can cause machine-wide denial of service&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhea-2024:4022</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:1486-1 — Security update for cosign</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:1486-1</link>
      <description>&lt;p&gt;Security update for cosign&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for cosign&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2024:1486-1</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1707 — Red Hat Advanced Cluster Security for Kubernetes: Mehrere Schwachstellen ermöglichen Offenlegung von Informationen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1707</link>
      <description>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Red Hat Advanced Cluster Security for Kubernetes ausnutzen, um Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Red Hat Advanced Cluster Security for Kubernetes ausnutzen, um Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1707</guid>
    </item>
  </channel>
</rss>
