-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Use default query selectors for Actions suites #18705
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
Conversation
These will wind up in `security-extended`, when previously they were not in any of the standard suites.
This ensures that it will remain in the default suite.
This ensures that it will remain in the default suite.
This ensures that it will be in `security-extended`, but not the default suite.
…-security-extended`
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.
Copilot reviewed 8 out of 8 changed files in this pull request and generated no comments.
Tip: Copilot only keeps its highest confidence comments to reduce noise and keep you focused. Learn more
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.
Looks reasonable, just some questions on change note.
@@ -0,0 +1,17 @@ | |||
--- | |||
category: queryMetadata |
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.
Can we indicate somehow this is breaking and that alerts from the moved queries will close for existing users?
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.
I've changed the category to breaking
and enhanced the description.
This PR switches the two primary Actions suites to use the same query selectors as all of the other languages. I've adjusted the severity and/or priority of several queries to make sure that they wind up in the right suite. The net changes in suite placement are:
Removed from both suites
These queries are not security-related.
if-expression-always-true/critical
if-expression-always-true/high
unnecessary-use-of-advanced-config
Demoted to
security-extended
unpinned-tag
Added to
security-extended
(previously not in either suite)Most of these are just lower-precision versions of queries from the default suite.
unversioned-immutable-action
envpath-injection/medium
envvar-injection/medium
code-injection/medium
artifact-poisoning/medium
untrusted-checkout/medium