Skip to content
Fencer Intel
medium 5.5

CVE-2022-36056 json

Vulnerabilities with blob verification in sigstore cosign

published 4y ago modified 2mo ago also BIT-cosign-2022-36056 , EUVD-2022-6744 , GHSA-8gw7-4j42-w388 , GO-2022-0998

cvss
5.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 4%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/sigstore/cosign 1.12.0
  • bitnami cosign 1.12.0
  • sigstore cosign 1.12.0
  • cosign SLE Module for Basesystem 15 SP4, openSUSE Leap 15.4 1.12.0-150400.3.6.1

suse advisories SUSE-SU-2022:3486-1

  • cosign openSUSE Tumbleweed 1.12.0-1.1

opensuse advisories openSUSE-SU-2024:12331-1

  • cosign Alpine 3.24, Alpine 3.23, Alpine 3.22 +5 more 1.12.1-r0

alpine advisories ALPINE-CVE-2022-36056

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2022-36056 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-36056 updated cvss 4.1

app-containers/cosign: false positive verification

  • Red Hat OpenShift Serverless openshift-serverless-1/openshift-serverless-1-client-kn-rhel8
    affected: no fix available “Fix deferred”
  • Red Hat RHACS 3.73 for RHEL 8 advanced-cluster-security/rhacs-main-rhel8 3.73.0-4, advanced-cluster-security/rhacs-scanner-rhel8 3.73.0-4
    fixed: vendor fix RHSA-2022:8827
  • Red Hat Advanced Cluster Security 3 advanced-cluster-security/rhacs-docs-rhel8, advanced-cluster-security/rhacs-roxctl-rhel8, advanced-cluster-security/rhacs-rhel8-operator, advanced-cluster-security/rhacs-scanner-db-rhel8, advanced-cluster-security/rhacs-scanner-slim-rhel8, advanced-cluster-security/rhacs-scanner-db-slim-rhel8 Red Hat RHACS 3.73 for RHEL 8 advanced-cluster-security/rhacs-docs-rhel8 3.73.0-4, advanced-cluster-security/rhacs-roxctl-rhel8 3.73.0-4, advanced-cluster-security/rhacs-rhel8-operator 3.73.0-4, advanced-cluster-security/rhacs-collector-rhel8 3.73.0-4, advanced-cluster-security/rhacs-operator-bundle 3.73.0-6, advanced-cluster-security/rhacs-central-db-rhel8 3.73.0-4, +4 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.15% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/sigstore/cosign/security/advisories/GHSA-8gw7-4j42-w388 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
GitHub 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
OSV 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/sigstore/cosign
<1.12.0
1.12.0
bitnami cosign
<1.12.0
1.12.0

Affected products

  • sigstore cosign

Classification

Weakness
  • CWE-347 Improper Verification of Cryptographic Signature

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.