OPENSUSE-SU-2024:13402-1

Vulnerability from csaf_opensuse - Published: 2024-06-15 00:00 - Updated: 2026-11-15 20:14
Summary
cosign-2.2.1-1.1 on GA media
Severity
Moderate
Notes
Title of the patch: cosign-2.2.1-1.1 on GA media
Description of the patch: These are all security issues fixed in the cosign-2.2.1-1.1 package on the GA media of openSUSE Tumbleweed.
Patchnames: openSUSE-Tumbleweed-2024-13402
Terms of use: CSAF 2.0 data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).
Affected products
Product Identifier Version Remediation
Unresolved product id: openSUSE Tumbleweed:cosign-0:2.2.1-1.1.aarch64 —
Vendor Fix
Unresolved product id: openSUSE Tumbleweed:cosign-0:2.2.1-1.1.ppc64le —
Vendor Fix
Unresolved product id: openSUSE Tumbleweed:cosign-0:2.2.1-1.1.s390x —
Vendor Fix
Unresolved product id: openSUSE Tumbleweed:cosign-0:2.2.1-1.1.x86_64 —
Vendor Fix
Threats
Impact moderate

{
  "document": {
    "aggregate_severity": {
      "namespace": "https://www.suse.com/support/security/rating/",
      "text": "moderate"
    },
    "category": "csaf_security_advisory",
    "csaf_version": "2.0",
    "distribution": {
      "text": "Copyright 2024 SUSE LLC. All rights reserved.",
      "tlp": {
        "label": "WHITE",
        "url": "https://www.first.org/tlp/"
      }
    },
    "lang": "en",
    "notes": [
      {
        "category": "summary",
        "text": "cosign-2.2.1-1.1 on GA media",
        "title": "Title of the patch"
      },
      {
        "category": "description",
        "text": "These are all security issues fixed in the cosign-2.2.1-1.1 package on the GA media of openSUSE Tumbleweed.",
        "title": "Description of the patch"
      },
      {
        "category": "details",
        "text": "openSUSE-Tumbleweed-2024-13402",
        "title": "Patchnames"
      },
      {
        "category": "legal_disclaimer",
        "text": "CSAF 2.0 data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).",
        "title": "Terms of use"
      }
    ],
    "publisher": {
      "category": "vendor",
      "contact_details": "https://www.suse.com/support/security/contact/",
      "name": "SUSE Product Security Team",
      "namespace": "https://www.suse.com/"
    },
    "references": [
      {
        "category": "external",
        "summary": "SUSE ratings",
        "url": "https://www.suse.com/support/security/rating/"
      },
      {
        "category": "self",
        "summary": "URL of this CSAF notice",
        "url": "https://ftp.suse.com/pub/projects/security/csaf/2024/opensuse-su-2024_13402-1.json"
      },
      {
        "category": "self",
        "summary": "SUSE CVE CVE-2023-46737 page",
        "url": "https://www.suse.com/security/cve/CVE-2023-46737/"
      }
    ],
    "title": "cosign-2.2.1-1.1 on GA media",
    "tracking": {
      "current_release_date": "2026-11-15T20:14:22Z",
      "generator": {
        "date": "2024-06-15T00:00:00Z",
        "engine": {
          "name": "cve-database.git:bin/generate-csaf.pl",
          "version": "1"
        }
      },
      "id": "openSUSE-SU-2024:13402-1",
      "initial_release_date": "2024-06-15T00:00:00Z",
      "revision_history": [
        {
          "date": "2024-06-15T00:00:00Z",
          "number": "1",
          "summary": "Current version"
        },
        {
          "date": "2026-09-20T20:59:59Z",
          "number": "2",
          "summary": "unknown changes"
        },
        {
          "date": "2026-11-15T20:14:22Z",
          "number": "3",
          "summary": "unknown changes"
        }
      ],
      "status": "final",
      "version": "3"
    }
  },
  "product_tree": {
    "branches": [
      {
        "branches": [
          {
            "branches": [
              {
                "category": "product_version",
                "name": "cosign-0:2.2.1-1.1.aarch64",
                "product": {
                  "name": "cosign-0:2.2.1-1.1.aarch64",
                  "product_id": "cosign-0:2.2.1-1.1.aarch64",
                  "product_identification_helper": {
                    "cpe": "cpe:2.3:a:sigstore:cosign:2.2.1:*:*:*:*:*:*:*",
                    "purl": "pkg:rpm/suse/cosign@2.2.1-1.1?arch=aarch64\u0026upstream=cosign-0:2.2.1-1.1.src.rpm"
                  }
                }
              }
            ],
            "category": "architecture",
            "name": "aarch64"
          },
          {
            "branches": [
              {
                "category": "product_version",
                "name": "cosign-0:2.2.1-1.1.ppc64le",
                "product": {
                  "name": "cosign-0:2.2.1-1.1.ppc64le",
                  "product_id": "cosign-0:2.2.1-1.1.ppc64le",
                  "product_identification_helper": {
                    "cpe": "cpe:2.3:a:sigstore:cosign:2.2.1:*:*:*:*:*:*:*",
                    "purl": "pkg:rpm/suse/cosign@2.2.1-1.1?arch=ppc64le\u0026upstream=cosign-0:2.2.1-1.1.src.rpm"
                  }
                }
              }
            ],
            "category": "architecture",
            "name": "ppc64le"
          },
          {
            "branches": [
              {
                "category": "product_version",
                "name": "cosign-0:2.2.1-1.1.s390x",
                "product": {
                  "name": "cosign-0:2.2.1-1.1.s390x",
                  "product_id": "cosign-0:2.2.1-1.1.s390x",
                  "product_identification_helper": {
                    "cpe": "cpe:2.3:a:sigstore:cosign:2.2.1:*:*:*:*:*:*:*",
                    "purl": "pkg:rpm/suse/cosign@2.2.1-1.1?arch=s390x\u0026upstream=cosign-0:2.2.1-1.1.src.rpm"
                  }
                }
              }
            ],
            "category": "architecture",
            "name": "s390x"
          },
          {
            "branches": [
              {
                "category": "product_version",
                "name": "cosign-0:2.2.1-1.1.x86_64",
                "product": {
                  "name": "cosign-0:2.2.1-1.1.x86_64",
                  "product_id": "cosign-0:2.2.1-1.1.x86_64",
                  "product_identification_helper": {
                    "cpe": "cpe:2.3:a:sigstore:cosign:2.2.1:*:*:*:*:*:*:*",
                    "purl": "pkg:rpm/suse/cosign@2.2.1-1.1?arch=x86_64\u0026upstream=cosign-0:2.2.1-1.1.src.rpm"
                  }
                }
              }
            ],
            "category": "architecture",
            "name": "x86_64"
          },
          {
            "branches": [
              {
                "category": "product_name",
                "name": "openSUSE Tumbleweed",
                "product": {
                  "name": "openSUSE Tumbleweed",
                  "product_id": "openSUSE Tumbleweed",
                  "product_identification_helper": {
                    "cpe": "cpe:/o:opensuse:tumbleweed"
                  }
                }
              }
            ],
            "category": "product_family",
            "name": "SUSE Linux Enterprise"
          }
        ],
        "category": "vendor",
        "name": "SUSE"
      }
    ],
    "relationships": [
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "cosign-0:2.2.1-1.1.aarch64 as component of openSUSE Tumbleweed",
          "product_id": "openSUSE Tumbleweed:cosign-0:2.2.1-1.1.aarch64"
        },
        "product_reference": "cosign-0:2.2.1-1.1.aarch64",
        "relates_to_product_reference": "openSUSE Tumbleweed"
      },
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "cosign-0:2.2.1-1.1.ppc64le as component of openSUSE Tumbleweed",
          "product_id": "openSUSE Tumbleweed:cosign-0:2.2.1-1.1.ppc64le"
        },
        "product_reference": "cosign-0:2.2.1-1.1.ppc64le",
        "relates_to_product_reference": "openSUSE Tumbleweed"
      },
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "cosign-0:2.2.1-1.1.s390x as component of openSUSE Tumbleweed",
          "product_id": "openSUSE Tumbleweed:cosign-0:2.2.1-1.1.s390x"
        },
        "product_reference": "cosign-0:2.2.1-1.1.s390x",
        "relates_to_product_reference": "openSUSE Tumbleweed"
      },
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "cosign-0:2.2.1-1.1.x86_64 as component of openSUSE Tumbleweed",
          "product_id": "openSUSE Tumbleweed:cosign-0:2.2.1-1.1.x86_64"
        },
        "product_reference": "cosign-0:2.2.1-1.1.x86_64",
        "relates_to_product_reference": "openSUSE Tumbleweed"
      }
    ]
  },
  "vulnerabilities": [
    {
      "cve": "CVE-2023-46737",
      "ids": [
        {
          "system_name": "SUSE CVE Page",
          "text": "https://www.suse.com/security/cve/CVE-2023-46737"
        }
      ],
      "notes": [
        {
          "category": "general",
          "text": "Cosign is a sigstore signing tool for OCI containers. Cosign is susceptible to a denial of service by an attacker controlled registry. An attacker who controls a remote registry can return a high number of attestations and/or signatures to Cosign and cause Cosign to enter a long loop resulting in an endless data attack. The root cause is that Cosign loops through all attestations fetched from the remote registry in pkg/cosign.FetchAttestations. The attacker needs to compromise the registry or make a request to a registry they control. When doing so, the attacker must return a high number of attestations in the response to Cosign. The result will be that the attacker can cause Cosign to go into a long or infinite loop that will prevent other users from verifying their data. In Kyvernos case, an attacker whose privileges are limited to making requests to the cluster can make a request with an image reference to their own registry, trigger the infinite loop and deny other users from completing their admission requests. Alternatively, the attacker can obtain control of the registry used by an organization and return a high number of attestations instead the expected number of attestations. The issue can be mitigated rather simply by setting a limit to the limit of attestations that Cosign will loop through. The limit does not need to be high to be within the vast majority of use cases and still prevent the endless data attack. This issue has been patched in version 2.2.1 and users are advised to upgrade.",
          "title": "CVE description"
        }
      ],
      "product_status": {
        "recommended": [
          "openSUSE Tumbleweed:cosign-0:2.2.1-1.1.aarch64",
          "openSUSE Tumbleweed:cosign-0:2.2.1-1.1.ppc64le",
          "openSUSE Tumbleweed:cosign-0:2.2.1-1.1.s390x",
          "openSUSE Tumbleweed:cosign-0:2.2.1-1.1.x86_64"
        ]
      },
      "references": [
        {
          "category": "external",
          "summary": "CVE-2023-46737",
          "url": "https://www.suse.com/security/cve/CVE-2023-46737"
        },
        {
          "category": "external",
          "summary": "SUSE Bug 1216933 for CVE-2023-46737",
          "url": "https://bugzilla.suse.com/1216933"
        }
      ],
      "remediations": [
        {
          "category": "vendor_fix",
          "details": "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n",
          "product_ids": [
            "openSUSE Tumbleweed:cosign-0:2.2.1-1.1.aarch64",
            "openSUSE Tumbleweed:cosign-0:2.2.1-1.1.ppc64le",
            "openSUSE Tumbleweed:cosign-0:2.2.1-1.1.s390x",
            "openSUSE Tumbleweed:cosign-0:2.2.1-1.1.x86_64"
          ]
        }
      ],
      "scores": [
        {
          "cvss_v3": {
            "baseScore": 3.1,
            "baseSeverity": "LOW",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L",
            "version": "3.1"
          },
          "products": [
            "openSUSE Tumbleweed:cosign-0:2.2.1-1.1.aarch64",
            "openSUSE Tumbleweed:cosign-0:2.2.1-1.1.ppc64le",
            "openSUSE Tumbleweed:cosign-0:2.2.1-1.1.s390x",
            "openSUSE Tumbleweed:cosign-0:2.2.1-1.1.x86_64"
          ]
        }
      ],
      "threats": [
        {
          "category": "impact",
          "date": "2024-06-15T00:00:00Z",
          "details": "moderate"
        }
      ],
      "title": "CVE-2023-46737"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.