Bug 13135

Summary: New CVEs are Historical
Product: [Yocto Project Subprojects] Security Response Tool Reporter: Ross Burton <ross.burton>
Component: GeneralAssignee: 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 2019-01-10 16:18:10 UTC
I copy/pasted the NIST 2018 data source to 2019, restarted srtool, and ... none of the 2019 CVEs are in triage.

But if I go to the CVE list they are there, with Historical state.
Comment 1 Ross Burton 2019-01-10 16:18:58 UTC
At a guess: is Historical the default state?  Should that be changed to New?
Comment 2 David Reyna 2019-01-12 19:28:34 UTC
commit ce03c55b2425fcb0efba606c539c071e9efcc2f8
Author: David Reyna <David.Reyna@windriver.com>
Date:   Sat Jan 12 10:48:17 2019 -0800

    srtool: improve CVE status assignments, add CVE 2019
    
    1. Add the CVE 2019 data soures for MITRE and NIST.
    2. Improve the CVE default status assignment system:
      * During the "Init" phase all CVEs default to HISTORICAL, unless they are
        within the CVE_INIT_NEW_DELTA date range. The value CVE_INIT_NEW_DELTA is
        defined in "bin/common/datasource.json", and is an out-of-box courtesy
        to provide some CVEs for triage in newly initialized systems. Changing
        the default value to '0' disabled this.
      * During the "Update" phase, CVEs default to NEW (and thus primed for
        triage)
      * Better separate the Init versus Update functions in "srtool_mitre.py" and
        "srtool_nist.py", and their respective datasource files.
      * Remove the post-process "preset_new()" in "srtool_common.py" in favor
        of directly computing the values in get_cve_default_status() in
        "srtool_mitre.py" and "srtool_nist.py", for speed and consistency.