<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>13135</bug_id>
          
          <creation_ts>2019-01-10 16:18:10 +0000</creation_ts>
          <short_desc>New CVEs are Historical</short_desc>
          <delta_ts>2019-01-22 21:14:04 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>6</classification_id>
          <classification>Yocto Project Subprojects</classification>
          <product>Security Response Tool</product>
          <component>General</component>
          <version>unspecified</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>2.7 M2</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Ross Burton">ross.burton</reporter>
          <assigned_to name="David Reyna">david.reyna</assigned_to>
          
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>No (bug/feature does not impact docs)</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>82738</commentid>
    <comment_count>0</comment_count>
    <who name="Ross Burton">ross.burton</who>
    <bug_when>2019-01-10 16:18:10 +0000</bug_when>
    <thetext>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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>82739</commentid>
    <comment_count>1</comment_count>
    <who name="Ross Burton">ross.burton</who>
    <bug_when>2019-01-10 16:18:58 +0000</bug_when>
    <thetext>At a guess: is Historical the default state?  Should that be changed to New?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>82769</commentid>
    <comment_count>2</comment_count>
    <who name="David Reyna">david.reyna</who>
    <bug_when>2019-01-12 19:28:34 +0000</bug_when>
    <thetext>commit ce03c55b2425fcb0efba606c539c071e9efcc2f8
Author: David Reyna &lt;David.Reyna@windriver.com&gt;
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 &quot;Init&quot; 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 &quot;bin/common/datasource.json&quot;, and is an out-of-box courtesy
        to provide some CVEs for triage in newly initialized systems. Changing
        the default value to &apos;0&apos; disabled this.
      * During the &quot;Update&quot; phase, CVEs default to NEW (and thus primed for
        triage)
      * Better separate the Init versus Update functions in &quot;srtool_mitre.py&quot; and
        &quot;srtool_nist.py&quot;, and their respective datasource files.
      * Remove the post-process &quot;preset_new()&quot; in &quot;srtool_common.py&quot; in favor
        of directly computing the values in get_cve_default_status() in
        &quot;srtool_mitre.py&quot; and &quot;srtool_nist.py&quot;, for speed and consistency.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>