<?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>13121</bug_id>
          
          <creation_ts>2019-01-04 15:27:23 +0000</creation_ts>
          <short_desc>CVE Resource information not available in SRTool</short_desc>
          <delta_ts>2019-01-12 18:34:13 +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>x86_64</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="Karin Julenius">karin.julenius</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>82679</commentid>
    <comment_count>0</comment_count>
    <who name="Karin Julenius">karin.julenius</who>
    <bug_when>2019-01-04 15:27:23 +0000</bug_when>
    <thetext>Preconditions/Environment
-------------------------
centos-release-7-6.1810.2.el7.centos.x86_64
Django==2.1.4
pytz==2018.7
SRTool commit b6d8d653dabcbd8d42ccb7f205bb58c7bf6f24cb

Triggering Action/Cause
-----------------------
Looking at the detail page of a specific CVE

Expectation
-----------
Under the headline &quot;References to Advisories, Solutions, and Tools&quot; there is a table of Hyperlinks that looks very similar to the same table at the corresponding page at nvd.nist.gov. I would expect the content to also be the same, i e if there is a &quot;Resource&quot; classification to one of the hyperlinks, I expect it to be seen. 

Actual Result
-------------
I cannot find a single CVE with Resource or Type information in the database:
sqlite&gt; select * from orm_cvereference where resource is not null;
sqlite&gt; select * from orm_cvereference where type is not null;
sqlite&gt; 


Reproducibility
---------------
10/10</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>82680</commentid>
    <comment_count>1</comment_count>
    <who name="David Reyna">david.reyna</who>
    <bug_when>2019-01-04 16:39:03 +0000</bug_when>
    <thetext>Hi Karin,

It is true that the CVE is indeed purposely patterned after the NIST page.

And it is also true that the &quot;resource&quot; and &quot;type&quot; fields are currently empty. 

  * When I did my first implementation, the JSON files from NIST did not include the &quot;Resource&quot;, &quot;Type&quot;, and &quot;Source&quot; fields. I did not worry about it at the time because the content visible at the NIST site seemed completely redundant with the actual hyperlink.

  * I just now looked again at NIST, and I see that they have since changed the interface. The &quot;Resource&quot; field now seems to be &apos;tag&apos; like entries, and the &quot;Type&quot; and &quot;Source&quot; fields are removed.

I will review the latest JSON format, and include the &quot;resource&quot; field if it present.

Thanks,
David</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>82681</commentid>
    <comment_count>2</comment_count>
    <who name="David Reyna">david.reyna</who>
    <bug_when>2019-01-04 17:09:47 +0000</bug_when>
    <thetext>And yes, it has been added to the NIST JSON schema:

&quot;references&quot;: 
  &quot;reference_data&quot;: [
    &quot;url&quot;: &quot;http://www.securityfocus.com/bid/103092&quot;, &quot;name&quot;: &quot;103092&quot;, &quot;tags&quot;: [], &quot;refsource&quot;: &quot;BID&quot;},
    &quot;url&quot;: &quot;http://www.securitytracker.com/id/1040180&quot;, &quot;name&quot;: &quot;1040180&quot;, &quot;tags&quot;: [&quot;Third Party Advisory&quot;, &quot;VDB Entry&quot;], &quot;refsource&quot;: &quot;SECTRACK&quot;},
    &quot;url&quot;: &quot;https://kb.juniper.net/JSA10828&quot;, &quot;name&quot;: &quot;https://kb.juniper.net/JSA10828&quot;, &quot;tags&quot;: [&quot;Mitigation&quot;, &quot;Patch&quot;, &quot;Vendor Advisory&quot;], &quot;refsource&quot;: &quot;CONFIRM&quot;}
 ]}</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>82685</commentid>
    <comment_count>3</comment_count>
    <who name="David Reyna">david.reyna</who>
    <bug_when>2019-01-05 02:28:36 +0000</bug_when>
    <thetext>Fix pushed:

commit e61223da184829d911c6247640abb81d08c7ab59</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>82694</commentid>
    <comment_count>4</comment_count>
    <who name="Karin Julenius">karin.julenius</who>
    <bug_when>2019-01-07 10:57:36 +0000</bug_when>
    <thetext>Hi!

Thank you for a quick fix!
However, some resource links look like they have been parsed  incorrectly, for instance first row in:

http://linux-srtool:8010/srtgui/cve/CVE-2015-8504</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>82695</commentid>
    <comment_count>5</comment_count>
    <who name="Karin Julenius">karin.julenius</who>
    <bug_when>2019-01-07 11:00:05 +0000</bug_when>
    <thetext>Sorry, for the internal link. I meant to paste this one:

https://nvd.nist.gov/vuln/detail/CVE-2015-8504</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>82703</commentid>
    <comment_count>6</comment_count>
    <who name="David Reyna">david.reyna</who>
    <bug_when>2019-01-07 18:30:06 +0000</bug_when>
    <thetext>New fix pushed:

   commit 89a07b2546cfed66ed833c0960ddfc2bc69be9fc

Changing the internal field separator from &apos;;&apos; to a tab key avoids parsing problems with CVE references like:

  http://git.qemu-project.org/?p=qemu.git;a=commitdiff;h=4c65fed8b...

- David</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>82767</commentid>
    <comment_count>7</comment_count>
    <who name="David Reyna">david.reyna</who>
    <bug_when>2019-01-12 18:34:13 +0000</bug_when>
    <thetext>commit 98b5bc41ed75b57de4376757a575458e72bf44c3
commit 89a07b2546cfed66ed833c0960ddfc2bc69be9fc
commit e61223da184829d911c6247640abb81d08c7ab59</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>