New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[v15] chore: Bump github.com/sigstore/cosign/v2 to 2.2.4 #40497
Conversation
This touches quite a lot of deps, so I gotta say it makes me a bit uneasy. WDYT? |
These CVEs might affect our use-case for cosign and are mainly important for users that use custom registries. If an attacker gains the ability of overriding the image they can cause denied of service. What do you think @hugoShaka ? |
I'm in favor of doing the update to fix the CVE, especially because the updater doesn't have memory limits by default. I walked through all the changelogs for 0.x direct dependencies are did not find anything obvious that would break for us. However, this PR causes an OTEL schema bump, and we end up with two conflicting schemas.
|
Yes, there are problems with otel, I'll chase those in the near future. |
8d95808
to
13ad166
Compare
Manual backport of #40485 to branch/v15.
Changelog: Updated cosign to address CVE-2024-29902 and CVE-2024-29903