13118 2019-01-03 16:39:59 +0000 New Vulnerability has Historical/Wontfix state 2020-06-24 22:33:52 +0000 1 1 6 Yocto Project Subprojects Security Response Tool General unspecified x86 Multiple RESOLVED FIXED Medium normal 3.2 M1 1 ross.burton david.reyna --- --- No (bug/feature does not impact docs) oldest_to_newest 82656 0 ross.burton 2019-01-03 16:39:59 +0000 I created a new Vulnerability for a number of CVEs, but the status has defaulted to Status: Historical, Outcome: Closed (won't fix). 82675 1 david.reyna 2019-01-04 05:22:40 +0000 1. New vulnerabilities by default inherit their status from the parent CVE. (a) Example CVE-xxxx with Priority: Undefined, Status: Historical -> VUL-xxxxx with Priority: Undefined, Status: Historical, Outcome: Open (b) Example CVE-xxxx with Priority: High, Status: Investigate -> VUL-xxxxx with Priority: High, Status: Investigate, Outcome: Open 2. New vulnerabilities created from the top bar "New Vulnerability" when in the Vulnerabilities table by default get these values (from orm/models.py): VUL-xxxxx with Priority: Low, Status: Investigate, Outcome: Open 3. QUESTION: I can change the default from CVEs to be more like #2? I can also at least force the Status to be "Investigate" and the Outcome to be "Open" since it is being explicitly created? 82733 2 ross.burton 2019-01-10 16:04:18 +0000 Forcing the status sounds like a better idea than copying Historical, yes. 84873 3 david.reyna 2019-09-05 04:40:15 +0000 This should be addressed with my pending bulk update.