Bug 13118 - New Vulnerability has Historical/Wontfix state
Summary: New Vulnerability has Historical/Wontfix state
Status: RESOLVED FIXED
Alias: None
Product: Security Response Tool
Classification: Yocto Project Subprojects
Component: General (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 3.2 M1
Assignee: David Reyna
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2019-01-03 16:39 UTC by Ross Burton
Modified: 2020-06-24 22:33 UTC (History)
0 users

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ross Burton 2019-01-03 16:39:59 UTC 
I created a new Vulnerability for a number of CVEs, but the status has defaulted to Status: Historical, Outcome: Closed (won't fix).
Comment 1 David Reyna 2019-01-04 05:22:40 UTC 
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?
Comment 2 Ross Burton 2019-01-10 16:04:18 UTC 
Forcing the status sounds like a better idea than copying Historical, yes.
Comment 3 David Reyna 2019-09-05 04:40:15 UTC 
This should be addressed with my pending bulk update.