CVE-2022-35930 Ability to bypass attestation verification in sigstore PolicyController
Attackers can bypass attestation verification in sigstore PolicyController, allowing unauthorized images into Kubernetes clusters.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2022-35930?
CVE-2022-35930 is a high-severity vulnerability in sigstore policy-controller, published on 4 Aug 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
PolicyController is a utility used to enforce supply chain policy in Kubernetes clusters. In versions prior to 0.2.1 PolicyController will report a false positive, resulting in an admission when it should not be admitted 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"). An example image that can be used to test this is `ghcr.io/distroless/static@sha256:dd7614b5a12bc4d617b223c588b4e0c833402b8f4991fb5702ea83afad1986e2`. Users should upgrade to version 0.2.1 to resolve this issue. There are no workarounds for users unable to upgrade.
Weakness: CWE-347
Which versions are affected by CVE-2022-35930?
3 open source packages ship an affected version, including github.com/sigstore/policy-controller. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/sigstore/policy-controller Go | All versions | 0.2.1 |
github.com/sigstore/policy-controller Go | All versions | 0.2.1 |
github.com/sigstore/policy-controller Go | All versions | 0.2.1 |
Products include Sigstore Policy Controller.
How do I fix CVE-2022-35930?
Upgrade github.com/sigstore/policy-controller to 0.2.1 or later.
Is CVE-2022-35930 being exploited?
There is no known exploitation of CVE-2022-35930 in the wild and no public exploit code.
Sources
Also known as GHSA-739f-hw6h-7wq8, GO-2022-0759.