| Summary: | Triage prediction isn't working | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Security Response Tool | Reporter: | Ross Burton <ross.burton> |
| Component: | General | Assignee: | David Reyna <david.reyna> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | ||
| Version: | unspecified | ||
| Target Milestone: | 2.7 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Ross Burton
2018-11-09 12:53:29 UTC
1. This limitation is on purpose and is temporary. The keyword calculations are currently disabled by default. This is because with installations that do not have historical CVE status data _all_ CVEs appear as "New", and to calculate this data for all CVEs would take a prohibitively long time. 2. The immediate solution is to perform a direct calculation for a set of CVEs, for example: $ ./bin/srtool_common.py --score-new-cves CVE-2018 This will score all of the "CVE-2018-*" CVEs. 3. The full solution will be: (a) Provide a user option to automatic calculate scores for all "New" CVEs, so that all CVEs that appear in the triage are already scored. This is intended for installations with up-to-date CVE historical status in place. (b) In the triage page, provide for on-demand score calculations for all selected CVEs in triage page, but add a 'New' date range filter specifically for installations without up-to-date CVE historical status in place. This will also require a progress bar of some form to advise users. The following has been implemented. 1. When the SRTool is first initialized, all imported existing CVEs are marked as "Historical". 2. Then, for the CVes that have been created within the last month, these are marked as "New". 3. If the user enables Defect System integration, then those imported Defects can reset their respective CVEs to the intended state, for example "New". 4. All of the "New" CVEs are automatically scored, for these and going forward for any subsequent new ones. 5. In this manner, the system is not overloaded in trying to score CVEs that are out of scope. |