Skip to content

cosign's `cosign verify-attestaton --type` can report a false positive if any attestation exists

High severity GitHub Reviewed Published Aug 4, 2022 in sigstore/cosign • Updated Jan 30, 2023

Package

gomod github.com/sigstore/cosign (Go)

Affected versions

< 1.10.1

Patched versions

1.10.1

Description

cosign verify-attestation used with the --type flag will report a false positive verification when:

  • There is at least one attestation with a valid signature
  • There are NO attestations of the type being verified (--type defaults to "custom")

This can happen when signing with a standard keypair and with "keyless" signing with Fulcio. Users should upgrade to cosign version 1.10.1 or greater for a patch. Currently the only workaround is to upgrade.

References

@priyawadhwa priyawadhwa published to sigstore/cosign Aug 4, 2022
Published by the National Vulnerability Database Aug 4, 2022
Published to the GitHub Advisory Database Aug 10, 2022
Reviewed Aug 10, 2022
Last updated Jan 30, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

EPSS score

0.242%
(64th percentile)

Weaknesses

CVE ID

CVE-2022-35929

GHSA ID

GHSA-vjxv-45g9-9296

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.