GHSA-xvrc-2wvh-49vc

    Dashboard / Vulnerabilities / GHSA-xvrc-2wvh-49vc

    GHSA-xvrc-2wvh-49vc

    Published: 14 Nov 2023Last Modified: 21 Aug 2024

    Summary: Gitsign's Rekor public keys fetched from upstream API instead of local TUF client.

    Details: ### Impact In certain versions of gitsign, Rekor public keys were fetched via the Rekor API, instead of through the local TUF client. If the upstream Rekor server happened to be compromised, gitsign clients could potentially be tricked into trusting incorrect signatures. There is no known compromise the default public good instance (`rekor.sigstore.dev`) - anyone using this instance is unlikely to be affected. ### Patches This was fixed in v0.8.0 via https://github.com/sigstore/gitsign/pull/399 ### Workarounds n/a ### References _Are there any links users can visit to find out more?_ https://docs.sigstore.dev/about/threat-model/#sigstore-threat-model

    References: https://github.com/sigstore/gitsign/security/advisories/GHSA-xvrc-2wvh-49vc, https://nvd.nist.gov/vuln/detail/CVE-2023-47122, https://github.com/sigstore/gitsign/pull/399, https://github.com/sigstore/gitsign/commit/cd66ccb03c86a3600955f0c15f6bfeb75f697236, https://docs.sigstore.dev/about/threat-model/#sigstore-threat-model, https://github.com/sigstore/gitsign

    Affected packages

    Package

    Name: github.com/sigstore/gitsign

    Purl: pkg:golang/github.com/sigstore/gitsign

    Affected ranges

    Type: SEMVER

    Events:

    Introduced- 0.6.0
    Fixed -0.8.0

    Affected versions

    Common Vulnerability Scoring System

    Attack Vector
    Network
    Adjacent
    Local
    Physical
    Privileges Required
    None
    Low
    High
    User Interaction
    None
    Required
    Scope
    Unchanged
    Changed
    Confidentiality
    None
    Low
    High
    Integrity
    None
    Low
    High
    Availability
    None
    Low
    High
    GHSA-xvrc-2wvh-49vc | CVE-DB