Gitsign is a keyless Sigstore to signing tool for Git commits with your a GitHub / OIDC identity. gitsign may select the wrong Rekor entry to use during online verification when multiple entries are returned by the log. gitsign uses Rekor's search API to fetch entries that apply to a signature being verified. The parameters used for the search are the public key and the payload. The search API returns entries that match either condition rather than both. When gitsign's credential cache is used, there can be multiple entries that use the same ephemeral keypair / signing certificate. As gitsign assumes both conditions are matched by Rekor, there is no additional validation that the entry's hash matches the payload being verified, meaning that the wrong entry can be used to successfully pass verification. Impact is minimal as while gitsign does not match the payload against the entry, it does ensure that the certificate matches. This would need to be exploited during the certificate validity window (10 minutes) by the key holder.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - Gitsign is a keyless Sigstore to signing tool for Git commits with your a GitHub / OIDC identity. gitsign
    may select the wrong Rekor entry to use during online verification when multiple entries are returned by
    the log. gitsign uses Rekor's search API to fetch entries that apply to a signature being verified. The
    parameters used for the search are the public key and the payload. The search API returns entries that
    match either condition rather than both. When gitsign's credential cache is used, there can be multiple
    entries that use the same ephemeral keypair / signing certificate. As gitsign assumes both conditions are
    matched by Rekor, there is no additional validation that the entry's hash matches the payload being
    verified, meaning that the wrong entry can be used to successfully pass verification. Impact is minimal as
    while gitsign does not match the payload against the entry, it does ensure that the certificate matches.
    This would need to be exploited during the certificate validity window (10 minutes) by the key holder.
    (CVE-2024-51746)

The remote SUSE Linux SLES15 / openSUSE 15 host has a package installed that is affected by multiple vulnerabilities as referenced in the SUSE-SU-2024:4042-1 advisory.

    - Update to version 0.0.20241112T145010 2024-11-12T14:50:10Z.
      Refs jsc#PED-11136       Go CVE Numbering Authority IDs added or updated with aliases:
      * GO-2024-3250 CVE-2024-51744 GHSA-29wx-vh33-7x7r

    - Update to version 0.0.20241108T172500 2024-11-08T17:25:00Z.
      Refs jsc#PED-11136       Go CVE Numbering Authority IDs added or updated with aliases:
      * GO-2024-3260 CVE-2024-45794 GHSA-q78v-cv36-8fxj
      * GO-2024-3262 CVE-2024-10975 GHSA-2w5v-x29g-jw7j

    - Update to version 0.0.20241106T172143 2024-11-06T17:21:43Z.
      Refs jsc#PED-11136       Go CVE Numbering Authority IDs added or updated with aliases:
      * GO-2024-3251 CVE-2024-10389 GHSA-q3rp-vvm7-j8jg
      * GO-2024-3252 CVE-2024-51746 GHSA-8pmp-678w-c8xx
      * GO-2024-3253 CVE-2024-48057 GHSA-ghx4-cgxw-7h9p
      * GO-2024-3254 CVE-2024-51735 GHSA-wvv7-wm5v-w2gv

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
412790	SCA: security update for github.com/sigstore/gitsign (GHSA-8pmp-678w-c8xx)	Tenable Cloud Security	SCA Checks	low
412790	SCA: security update for github.com/sigstore/gitsign (GHSA-8pmp-678w-c8xx)	Tenable Self-Hosted Container Security	SCA Checks	low
212587	SUSE SLES15 / openSUSE 15 Security Update : govulncheck-vulndb (SUSE-SU-2024:4042-1)	Nessus	SuSE Local Security Checks	high

Detections

Analytics

CVE-2024-51746

low

Tenable Plugins

low

low

high