Bug 13134 - Doesn't fetch 2019 CVE data
Summary: Doesn't fetch 2019 CVE data
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: 2.7 M2
Assignee: David Reyna
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2019-01-10 16:02 UTC by Ross Burton
Modified: 2019-01-22 21:12 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

Note You need to log in before you can comment on or make changes to this bug.
Description Ross Burton 2019-01-10 16:02:33 UTC
MITRE and NIST backends have hardcoded date configurations, but no 2019 entries.

Would it be better to have templates for these which are generated for years between a specific start date and now?
Comment 1 David Reyna 2019-01-11 19:21:05 UTC
1) "MITRE and NIST backends have hardcoded date configurations, but no 2019 entries."

I will add the CVE-2019 entries today as part of the default setup. 

FYI, my original intent is that each adopter decides which years are relevant to them. I set 2015 to 2018 as automatic defaults just to get things going. It is however quite logical to add 2019 as part of the default set, so thanks for the reminder. 

2) "MITRE and NIST backends have hardcoded date configurations, but no 2019 entries. Would it be better to have templates for these which are generated for years between a specific start date and now?"

Because each of the years are hard coded to specific upstream data and meta files,  and because processing each year takes a long time, I would like to keep them separate so that they are easier to manage.

Besides, NIST could change their model at any time, and I want to stay flexible.

- David
Comment 2 David Reyna 2019-01-12 19:32:13 UTC
commit ce03c55b2425fcb0efba606c539c071e9efcc2f8

The 'status' processing has been fixed in #13135.

To move the already scanned CVE-2019 records to the 'NEW' status, you can:
  * Go to "Management > Triage"
  * Select "HISTORICAL" records
  * Click "Triage" button
  * Filter on "CVE-2019"
  * Click "Select All"
  * Click and accept "New"
  * Repeat the above two steps until all are moved