cosign is a container signing and verification utility. In versions prior to 1.10.1 cosign can report a false positive if any attestation exists. `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 and 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. This vulnerability can be reproduced with the `distroless.dev/static@sha256:dd7614b5a12bc4d617b223c588b4e0c833402b8f4991fb5702ea83afad1986e2` image. This image has a `vuln` attestation but not an `spdx` attestation. However, if you run `cosign verify-attestation --type=spdx` on this image, it incorrectly succeeds. This issue has been addressed in version 1.10.1 of cosign. Users are advised to upgrade. There are no known workarounds for this issue.

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

  - cosign is a container signing and verification utility. In versions prior to 1.10.1 cosign can report a
    false positive if any attestation exists. `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 and
    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. This vulnerability can be
    reproduced with the
    `distroless.dev/static@sha256:dd7614b5a12bc4d617b223c588b4e0c833402b8f4991fb5702ea83afad1986e2` image.
    This image has a `vuln` attestation but not an `spdx` attestation. However, if you run `cosign verify-
    attestation --type=spdx` on this image, it incorrectly succeeds. This issue has been addressed in version
    1.10.1 of cosign. Users are advised to upgrade. There are no known workarounds for this issue.
    (CVE-2022-35929)

The remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 / openSUSE 15 host has a package installed that is affected by a vulnerability as referenced in the SUSE-SU-2022:2877-1 advisory.

    - Updated to 1.10.1 (jsc#SLE-23879):
      - CVE-2022-35929: Fixed an issue where cosign verify-attestation --type         could report false positives when there was at least one attestation         with a valid signature and there were no attestations of the type         being verified (bsc#1202157).

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

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

ID	Name	Product	Family	Severity
419396	SCA: security update for github.com/sigstore/cosign (GHSA-vjxv-45g9-9296)	Tenable Cloud Security	SCA Checks	critical
419396	SCA: security update for github.com/sigstore/cosign (GHSA-vjxv-45g9-9296)	Tenable Self-Hosted Container Security	SCA Checks	critical
403908	Alpine: multiple cosign packages: security update to 1.10.1-r0	Tenable Cloud Security	Alpine Linux Local Security Checks	critical
403908	Alpine: multiple cosign packages: security update to 1.10.1-r0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	critical
164366	SUSE SLED15 / SLES15 / openSUSE 15 Security Update : cosign (SUSE-SU-2022:2877-1)	Nessus	SuSE Local Security Checks	critical
409100	Alpine: multiple cosign packages, multiple sget packages: security update to 1.9.0-r2 (deprecated)	Tenable Cloud Security	Alpine Linux Local Security Checks	critical
409100	Alpine: multiple cosign packages, multiple sget packages: security update to 1.9.0-r2 (deprecated)	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	critical

Detections

Analytics

CVE-2022-35929

critical

Tenable Plugins

critical

critical

critical

critical

critical

critical

critical