CVE-2022-23649

描述

Cosign provides container signing, verification, and storage in an OCI registry for the sigstore project. Prior to version 1.5.2, Cosign can be manipulated to claim that an entry for a signature exists in the Rekor transparency log even if it doesn't. This requires the attacker to have pull and push permissions for the signature in OCI. This can happen with both standard signing with a keypair and "keyless signing" with Fulcio. If an attacker has access to the signature in OCI, they can manipulate cosign into believing the entry was stored in Rekor even though it wasn't. The vulnerability has been patched in v1.5.2 of Cosign. The `signature` in the `signedEntryTimestamp` provided by Rekor is now compared to the `signature` that is being verified. If these don't match, then an error is returned. If a valid bundle is copied to a different signature, verification should fail. Cosign output now only informs the user that certificates were verified if a certificate was in fact verified. There is currently no known workaround.

如何修補 CVE-2022-23649

要修補 CVE-2022-23649,請將受影響套件升級到下列已修補版本。

• —升級至 1.5.2 或更新版本
• —升級至 1.5.2 或更新版本
• —升級至 1.5.2 或更新版本

CVE-2022-23649 正在被利用嗎?

低 — EPSS 為 0.2%,目前沒有觀察到大規模利用活動。

受影響套件(3)

• from 0, < 1.5.2
• from 0, < 1.5.2
• from 0, < 1.5.2

CVSS 分數

參考連結(5)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2022-23649
• WEBgithub.com/sigstore/cosign
• WEBgithub.com/sigstore/cosign/commit/96d410a6580e4e81d24d112a0855c70ca3fb5b49
• WEBgithub.com/sigstore/cosign/releases/tag/v1.5.2