forked from MetLife/github-mcp-server
-
Notifications
You must be signed in to change notification settings - Fork 0
fix(security): remediate SonarQube vulnerabilities in discussions.go #80
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
devin-ai-integration
wants to merge
1
commit into
main
Choose a base branch
from
devin/1770237075-sonarqube-discussions-fixes
base: main
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.
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
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.
🟡 ListDiscussionCategories pagination parameters are validated but silently ignored in the GraphQL query
The
ListDiscussionCategoriesfunction accepts pagination parameters (first,last,after,before), decodes them from the request, and validates them via the newly extractedvalidatePaginationParamsfunction, but the GraphQL query at line 361 hardcodesdiscussionCategories(first: 100)and never uses any of the user-supplied pagination values.Root Cause and Impact
The
params.First,params.Last,params.After, andparams.Beforefields are decoded atpkg/github/discussions.go:334-341and validated at line 346, but the GraphQL query struct tag at line 361 is hardcoded:`graphql:"discussionCategories(first: 100)"`And the
varsmap at lines 364-367 only includesownerandrepo:Impact: Users who pass
first,last,after, orbeforeparameters will receive no error (validation passes), but their pagination preferences are completely ignored. The query always returns the first 100 categories. This is particularly misleading now thatvalidatePaginationParamshas been extracted as a shared utility, suggesting pagination is properly implemented.(Refers to line 361)
Prompt for agents
Was this helpful? React with 👍 or 👎 to provide feedback.