-
-
Notifications
You must be signed in to change notification settings - Fork 991
docs(helm): fix documentation regarding chart signature verification #3420
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
Open
M0NsTeRRR
wants to merge
1
commit into
develop
Choose a base branch
from
fix/helm-docs-verification
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+7
−12
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: seerr-team/seerr
Length of output: 3800
🏁 Script executed:
Repository: seerr-team/seerr
Length of output: 38823
🌐 Web query:
Cosign verify-attestation --certificate-identity-regexp MatchString regular expression anchors certificate identity documentation💡 Result:
The --certificate-identity-regexp flag in the Cosign verify-attestation command accepts a regular expression to validate the certificate identity [1][2]. It uses the Go regular expression syntax (RE2), which is documented at https://golang.org/s/re2syntax [1][2]. Crucially, the regular expression used with this flag is unanchored by default [3][4]. This means the regex engine will perform a substring match, which can lead to security vulnerabilities where an attacker could forge an identity that contains your expected string (e.g., a branch or tag name containing your intended pattern) [3][4]. To ensure secure verification, you must manually include string anchors in your regular expression [3][4]: - Use the caret (^) anchor to match the beginning of the string [3][4]. - Use the dollar sign ($) anchor to match the end of the string [3][4]. For example, instead of using a pattern like https://github.com/org/repo/.*, which is vulnerable to substring matching, you should use an anchored pattern such as ^https://github\.com/org/repo/\.github/workflows/workflow\.yml@refs/tags/v[0-9]+\.[0-9]+\.[0-9]+$ [3][5][4]. Failing to anchor the expression allows any identity that simply contains the specified substring to pass verification [3][4].
Citations:
🏁 Script executed:
Repository: seerr-team/seerr
Length of output: 1604
🏁 Script executed:
Repository: seerr-team/seerr
Length of output: 5142
Use exact identity matching for the fixed workflow identity.
Replace
--certificate-identity-regexpwith--certificate-identityat lines 342, 347, and 358. The current expression uses unescaped dots and unanchored matching.If the chart CycloneDX attestation is intended, add a matching
cosign atteststep to.github/workflows/helm.yml. Otherwise, remove thecosign verify-attestationexample because the workflow only signs the chart.🤖 Prompt for AI Agents
Source: MCP tools