Project:Security/Bug Searching
This document gives tips and hints for helping filter security-related bugzilla bugs.
Bug Searching
All Security Bugs
For identifying all security-related bugs, use the Bugzilla query page and set the following fields:
- Product: select "Gentoo Security"
- Status: set this to the type of bug you want to search for (i.e. closed bugs, open bugs, etc.)
This will give you a list of all security bugs in our system (or at least the ones that are properly assigned). You can set the query to only display Vulnerabilities, Kernel issues, or other subsets of Security bugs by setting the Component
"Mark stable" Arch Bugs
When a package has had a security patch applied, it typically needs to be tested before being marked stable on affected architectures. To identify all bugs where a particular arch needs to mark a package stable, use the query page and set the following fields:
- Product: select "Gentoo Security"
- Status: set this to "New", "Assigned" and "Reopened" (i.e. don't search for bugs that are closed)
- Email and Numbering: Any of: "CC list member" should be set to "contains <arch>@gentoo.org"
When a package gets patched and requires testing, the security team will CC all relevant arches on that particular bug and request that they test and mark the package as stable on their architecture. Thus, by using the search criteria described above, you'll be able to easily see what bugs require attention for a particular arch.
To make this report effective, it's very important that arch teams remember to remove themselves from the CC list once they have stabilized a package.
For unsupported arches, bugs may be closed without the package being marked stable on that particular architecture. Thus, developers for these architectures may wish to include closed bugs in their queries. (For an explanation of "supported" vs. "unsupported" architectures, please see the Vulnerability Treatment Policy .)
Architecture Security Liaisons will need additional queries to catch bugs that require their participation. Those bugs could be for instance SEMI-PUBLIC ranked bugs that need to be marked stable in the tree, or CONFIDENTIAL bugs that have prestable testing in Bugzilla only. To get a list of these bugs, use the query page and set the following fields:
- Product: select "Gentoo Security"
- Status: set this to "New", "Assigned" and "Reopened" (i.e. don't search for bugs that are closed)
- Email and Numbering: Any of: "CC list member" should be set to "contains <login>@gentoo.org" where <login> is the Gentoo username of the Liaison
- Advanced Searching Using Boolean Charts: "Group" should be set to "is equal to" and the input field should read "Security".
Bugzilla queries that might be helpful
Gentoo Security Team members and Padawans might find these queries helpful. Except from false positives, bugs listed in these queries need attention from the Security Team.
- Stale stable , display all open bugs that have "[stable]" in Whiteboard, but no arches in CC.
- GLSA vote , list of bugs that are fixed in the tree, bug have no GLSA decision yet.
- Unhandled bugs , bugs that are in no known (security) whiteboard state.
- No CVE , bugs that carry no CVE identifier in their title.
This page is based on a document formerly found on our main website gentoo.org.
The following people contributed to the original document: Kurt Lieber, Robert Buchholz, Tobias Heinlein
They are listed here because wiki history does not allow for any external attribution. If you edit the wiki article, please do not add yourself here; your contributions are recorded on each article's associated history page.