Improper Verification of Cryptographic Signature Affecting cosign package, versions <1.12.0-150400.3.6.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.01% (1st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES154-COSIGN-3038531
  • published2 Oct 2022
  • disclosed1 Oct 2022

Introduced: 1 Oct 2022

CVE-2022-36056  (opens in a new tab)
CWE-347  (opens in a new tab)

How to fix?

Upgrade SLES:15.4 cosign to version 1.12.0-150400.3.6.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream cosign package and not the cosign package as distributed by SLES. See How to fix? for SLES:15.4 relevant fixed versions and status.

Cosign is a project under the sigstore organization which aims to make signatures invisible infrastructure. In versions prior to 1.12.0 a number of vulnerabilities have been found in cosign verify-blob, where Cosign would successfully verify an artifact when verification should have failed. First a cosign bundle can be crafted to successfully verify a blob even if the embedded rekorBundle does not reference the given signature. Second, when providing identity flags, the email and issuer of a certificate is not checked when verifying a Rekor bundle, and the GitHub Actions identity is never checked. Third, providing an invalid Rekor bundle without the experimental flag results in a successful verification. And fourth an invalid transparency log entry will result in immediate success for verification. Details and examples of these issues can be seen in the GHSA-8gw7-4j42-w388 advisory linked. Users are advised to upgrade to 1.12.0. There are no known workarounds for these issues.

CVSS Base Scores

version 3.1