{"id":"CVE-2024-29902","aliases":["BIT-cosign-2024-29902","EUVD-2024-1155","GHSA-88jx-383q-w4qc","GO-2024-2718","RHEA-2024:4022","SUSE-SU-2024:1486-1","SUSE-SU-2024:1486-2","openSUSE-SU-2024:13863-1","openSUSE-SU-2024:13903-1"],"status":"published","title":"Cosign vulnerable to system-wide denial of service via malicious attachments","description":"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.","severity":{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:N/A:H","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.00658,"percentile":0.51785,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-770"],"published":"2024-04-10T22:28:19Z","modified":"2026-10-28T02:30:34Z","fixes":[{"ecosystem":"Go","package":"github.com/sigstore/cosign/v2","fixed_in":["2.2.4"],"sources":["ghsa","osv"]},{"ecosystem":"Bitnami","package":"cosign","fixed_in":["2.2.4"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"Go","package":"github.com/sigstore/cosign","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"2.2.3"}]}]},{"source":"ghsa","ecosystem":"Go","package":"github.com/sigstore/cosign/v2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"2.2.3"},{"fixed":"2.2.4"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"cosign","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.2.4"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/sigstore/cosign","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"2.2.3"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/sigstore/cosign/v2","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.2.4"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/sigstore/cosign","ranges":[{"type":"SEMVER","events":[{"introduced":"0"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/sigstore/cosign/v2","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.2.4"}]}]},{"source":"osv","ecosystem":"Red Hat:openshift_pipelines:1.15::el8","package":"openshift-pipelines-client","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.15.0-11496.el8"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openshift_pipelines:1.15::el8","package":"openshift-pipelines-client-redistributable","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.15.0-11496.el8"}]}],"bundled":5},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP5","package":"cosign","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.4-150400.3.20.1"}]}],"bundled":2},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"cosign","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.4-150400.3.20.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"cosign","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.4-150400.3.20.1"}]}],"bundled":2},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"cosign","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.4-150400.3.20.1"}]}],"bundled":2},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"cosign","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.4-1.1"}]}],"bundled":2},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"teleport","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.2.4-1.1"}]}],"bundled":3}],"products":[{"vendor":"sigstore","product":"cosign"}],"references":[{"url":"https://github.com/sigstore/cosign/security/advisories/GHSA-88jx-383q-w4qc","tags":["x_refsource_CONFIRM","x_transferred","Vendor Advisory","advisory","web","article"]},{"url":"https://github.com/sigstore/cosign/commit/629f5f8fa672973503edde75f84dcd984637629e","tags":["x_refsource_MISC","x_transferred","Patch","fix","web"]},{"url":"https://github.com/google/go-containerregistry/blob/a0658aa1d0cc7a7f1bcc4a3af9155335b6943f40/pkg/v1/remote/layer.go#L36-L40","tags":["x_refsource_MISC","x_transferred","Product","web"]},{"url":"https://github.com/sigstore/cosign/blob/9bc3ee309bf35d2f6e17f5d23f231a3d8bf580bc/pkg/oci/remote/remote.go#L228-L239","tags":["x_refsource_MISC","x_transferred","Product","web"]},{"url":"https://github.com/sigstore/cosign/releases/tag/v2.2.4","tags":["x_refsource_MISC","x_transferred","Release Notes","article","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-29902","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-88jx-383q-w4qc"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/29xxx/CVE-2024-29902.json","tags":["advisory"]},{"url":"https://github.com/sigstore/cosign","tags":["package"]},{"url":"https://access.redhat.com/errata/RHEA-2024:4022","tags":["advisory"]},{"url":"https://docs.openshift.com/container-platform/4.14/cli_reference/tkn_cli/installing-tkn.html","tags":["article"]},{"url":"https://issues.redhat.com/browse/SRVKP-3124","tags":["article"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2024/rhea-2024_4022.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-45288","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2268273","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-45288","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-45288","tags":["advisory"]},{"url":"https://nowotarski.info/http2-continuation-flood/","tags":["article"]},{"url":"https://pkg.go.dev/vuln/GO-2024-2687","tags":["advisory"]},{"url":"https://www.kb.cert.org/vuls/id/421644","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-28110","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2268372","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-28110","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-28110","tags":["advisory"]},{"url":"https://github.com/cloudevents/sdk-go/security/advisories/GHSA-5pf6-2qwx-pxm2","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-28180","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2268854","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-28180","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-28180","tags":["advisory"]},{"url":"https://github.com/go-jose/go-jose/security/advisories/GHSA-c5q2-7r4c-mv6g","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-29902","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2274508","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-29902","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-29903","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2274504","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-29903","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-29903","tags":["advisory"]},{"url":"https://github.com/sigstore/cosign/security/advisories/GHSA-95pr-fxf5-86gv","tags":["article"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20241486-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1222835","tags":["report"]},{"url":"https://bugzilla.suse.com/1222837","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2024-29902","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-29903","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20241486-2/","tags":["advisory"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2023-45288","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-32650","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2024-29902","title":"Cosign vulnerable to system-wide denial of service via malicious attachments","description":"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.","status":"published","published":"2024-04-10T22:28:19.788Z","modified":"2024-08-02T01:17:58.609Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:N/A:H","level":"medium","assessor":"cna"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T14:34:14.985673Z"}],"euvd":[{"id":"EUVD-2024-1155","description":"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.","status":"published","published":"2024-04-10T22:28:19Z","modified":"2024-08-02T01:17:58Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-03T03:50:25.628684Z"}],"ghsa":[{"id":"GHSA-88jx-383q-w4qc","title":"Cosign malicious attachments can cause system-wide denial of service","description":"### Summary\nA 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.\n\n### Details\nThe 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.\n\nThe root cause is that Cosign reads the contents of the attachments entirely into memory on line 238 below:\n\nhttps://github.com/sigstore/cosign/blob/9bc3ee309bf35d2f6e17f5d23f231a3d8bf580bc/pkg/oci/remote/remote.go#L228-L239\n\n...and prior to that, neither Cosign nor go-containerregistry checks the size of the attachment and enforces a max cap. In the case of a remote layer of `f *attached`, go-containerregistry will invoke this API:\n\nhttps://github.com/google/go-containerregistry/blob/a0658aa1d0cc7a7f1bcc4a3af9155335b6943f40/pkg/v1/remote/layer.go#L36-L40\n```golang\nfunc (rl *remoteLayer) Compressed() (io.ReadCloser, error) {\n\t// We don't want to log binary layers -- this can break terminals.\n\tctx := redact.NewContext(rl.ctx, \"omitting binary blobs from logs\")\n\treturn rl.fetcher.fetchBlob(ctx, verify.SizeUnknown, rl.digest)\n}\n```\n\nNotice that the second argument to `rl.fetcher.fetchBlob` is `verify.SizeUnknown` which results in not using the `io.LimitReader` in `verify.ReadCloser`:\nhttps://github.com/google/go-containerregistry/blob/a0658aa1d0cc7a7f1bcc4a3af9155335b6943f40/internal/verify/verify.go#L82-L100\n```golang\nfunc ReadCloser(r io.ReadCloser, size int64, h v1.Hash) (io.ReadCloser, error) {\n\tw, err := v1.Hasher(h.Algorithm)\n\tif err != nil {\n\t\treturn nil, err\n\t}\n\tr2 := io.TeeReader(r, w) // pass all writes to the hasher.\n\tif size != SizeUnknown {\n\t\tr2 = io.LimitReader(r2, size) // if we know the size, limit to that size.\n\t}\n\treturn \u0026and.ReadCloser{\n\t\tReader: \u0026verifyReader{\n\t\t\tinner:    r2,\n\t\t\thasher:   w,\n\t\t\texpected: h,\n\t\t\twantSize: size,\n\t\t},\n\t\tCloseFunc: r.Close,\n\t}, nil\n}\n```\n\n### Impact\nThis 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. \n\n### Remediation\nUpdate to the latest version of Cosign, which limits the number of attachments. An environment variable can override this value.","status":"published","published":"2024-04-11T17:05:01Z","modified":"2024-04-11T17:05:02Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T14:37:42.744468Z"}],"nvd":[{"id":"CVE-2024-29902","description":"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.","status":"published","published":"2024-04-10T23:15:06.92Z","modified":"2026-06-17T07:23:20.123Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:N/A:H","level":"medium","assessor":"secondary"},{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T14:09:49.255123Z"}],"osv":[{"id":"CVE-2024-29902","title":"Cosign vulnerable to system-wide denial of service via malicious attachments","description":"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.","status":"published","published":"2024-04-10T22:28:19.788Z","modified":"2026-10-28T02:30:34.22041219Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T15:44:40.06138Z"},{"id":"GHSA-88jx-383q-w4qc","title":"Cosign malicious attachments can cause system-wide denial of service","description":"### Summary\nA 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.\n\n### Details\nThe 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.\n\nThe root cause is that Cosign reads the contents of the attachments entirely into memory on line 238 below:\n\nhttps://github.com/sigstore/cosign/blob/9bc3ee309bf35d2f6e17f5d23f231a3d8bf580bc/pkg/oci/remote/remote.go#L228-L239\n\n...and prior to that, neither Cosign nor go-containerregistry checks the size of the attachment and enforces a max cap. In the case of a remote layer of `f *attached`, go-containerregistry will invoke this API:\n\nhttps://github.com/google/go-containerregistry/blob/a0658aa1d0cc7a7f1bcc4a3af9155335b6943f40/pkg/v1/remote/layer.go#L36-L40\n```golang\nfunc (rl *remoteLayer) Compressed() (io.ReadCloser, error) {\n\t// We don't want to log binary layers -- this can break terminals.\n\tctx := redact.NewContext(rl.ctx, \"omitting binary blobs from logs\")\n\treturn rl.fetcher.fetchBlob(ctx, verify.SizeUnknown, rl.digest)\n}\n```\n\nNotice that the second argument to `rl.fetcher.fetchBlob` is `verify.SizeUnknown` which results in not using the `io.LimitReader` in `verify.ReadCloser`:\nhttps://github.com/google/go-containerregistry/blob/a0658aa1d0cc7a7f1bcc4a3af9155335b6943f40/internal/verify/verify.go#L82-L100\n```golang\nfunc ReadCloser(r io.ReadCloser, size int64, h v1.Hash) (io.ReadCloser, error) {\n\tw, err := v1.Hasher(h.Algorithm)\n\tif err != nil {\n\t\treturn nil, err\n\t}\n\tr2 := io.TeeReader(r, w) // pass all writes to the hasher.\n\tif size != SizeUnknown {\n\t\tr2 = io.LimitReader(r2, size) // if we know the size, limit to that size.\n\t}\n\treturn \u0026and.ReadCloser{\n\t\tReader: \u0026verifyReader{\n\t\t\tinner:    r2,\n\t\t\thasher:   w,\n\t\t\texpected: h,\n\t\t\twantSize: size,\n\t\t},\n\t\tCloseFunc: r.Close,\n\t}, nil\n}\n```\n\n### Impact\nThis 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. \n\n### Remediation\nUpdate to the latest version of Cosign, which limits the number of attachments. An environment variable can override this value.","status":"published","published":"2024-04-11T17:05:01Z","modified":"2026-09-10T03:50:12.472087804Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T15:46:42.077781Z"},{"id":"RHEA-2024:4022","title":"Red Hat Enhancement Advisory: Red Hat OpenShift Pipelines Client tkn for 1.15.0 release","status":"published","published":"2025-02-26T10:05:17Z","modified":"2026-10-16T10:03:20Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:58.636919Z"},{"id":"BIT-cosign-2024-29902","title":"Cosign vulnerable to system-wide denial of service via malicious attachments","description":"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.","status":"published","published":"2024-04-12T07:17:20.659Z","modified":"2026-09-08T08:46:03.197405228Z","updated_at":"2026-11-02T15:28:28.70813Z"},{"id":"GO-2024-2718","title":"Cosign malicious attachments can cause system-wide denial of service in github.com/sigstore/cosign","description":"Cosign malicious attachments can cause system-wide denial of service in github.com/sigstore/cosign","status":"published","published":"2024-06-05T15:10:52Z","modified":"2026-02-04T03:18:34.975942Z","updated_at":"2026-11-02T15:47:01.453823Z"},{"id":"openSUSE-SU-2024:13863-1","title":"cosign-2.2.4-1.1 on GA media","description":"These are all security issues fixed in the cosign-2.2.4-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T02:52:41.516569Z","updated_at":"2026-11-02T16:58:36.662953Z"},{"id":"openSUSE-SU-2024:13903-1","title":"teleport-15.2.4-1.1 on GA media","description":"These are all security issues fixed in the teleport-15.2.4-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T03:52:22.710059Z","updated_at":"2026-11-02T16:58:36.662953Z"},{"id":"SUSE-SU-2024:1486-1","title":"Security update for cosign","description":"This update for cosign fixes the following issues:\n\n- CVE-2024-29902: Fixed denial of service on host machine via remote image with a malicious attachments (bsc#1222835)\n- CVE-2024-29903: Fixed denial of service on host machine via malicious software artifacts (bsc#1222837)\n\nOther fixes:\n- Updated to 2.2.4 (jsc#SLE-23879)\n    * Fixes for GHSA-88jx-383q-w4qc and GHSA-95pr-fxf5-86gv (#3661)\n    * ErrNoSignaturesFound should be used when there is no signature attached to an image. (#3526)\n    * fix semgrep issues for dgryski.semgrep-go ruleset (#3541)\n    * Honor creation timestamp for signatures again (#3549)\n  * Features\n    * Adds Support for Fulcio Client Credentials Flow, and Argument to Set Flow Explicitly (#3578)\n","status":"published","published":"2024-05-02T05:33:11Z","modified":"2026-02-04T03:54:05.292138Z","updated_at":"2026-11-02T15:53:54.652421Z"},{"id":"SUSE-SU-2024:1486-2","title":"Security update for cosign","description":"This update for cosign fixes the following issues:\n\n- CVE-2024-29902: Fixed denial of service on host machine via remote image with a malicious attachments (bsc#1222835)\n- CVE-2024-29903: Fixed denial of service on host machine via malicious software artifacts (bsc#1222837)\n\nOther fixes:\n- Updated to 2.2.4 (jsc#SLE-23879)\n    * Fixes for GHSA-88jx-383q-w4qc and GHSA-95pr-fxf5-86gv (#3661)\n    * ErrNoSignaturesFound should be used when there is no signature attached to an image. (#3526)\n    * fix semgrep issues for dgryski.semgrep-go ruleset (#3541)\n    * Honor creation timestamp for signatures again (#3549)\n  * Features\n    * Adds Support for Fulcio Client Credentials Flow, and Argument to Set Flow Explicitly (#3578)\n","status":"published","published":"2024-06-18T11:05:34Z","modified":"2026-02-04T03:57:15.727347Z","updated_at":"2026-11-02T15:53:54.652421Z"}]}}