<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: CVSS rating for Meltdown and Spectre in Tech Talk</title>
    <link>https://community.isc2.org/t5/Tech-Talk/CVSS-rating-for-Meltdown-and-Spectre/m-p/4972#M193</link>
    <description>The risk against integrity is a secondary risk and, with the same logic, availability risk should also be none-zero. Because with the right password recovered it's also possible to shut down services or do other nasty stuff. I am not sure you should take into account these secondary risks when scoring CVSS because confidentiality risks would mostly imply risks to I &amp;amp; A, so for clarity is better to only score the primary risks?</description>
    <pubDate>Mon, 08 Jan 2018 10:45:22 GMT</pubDate>
    <dc:creator>Ewald</dc:creator>
    <dc:date>2018-01-08T10:45:22Z</dc:date>
    <item>
      <title>CVSS rating for Meltdown and Spectre</title>
      <link>https://community.isc2.org/t5/Tech-Talk/CVSS-rating-for-Meltdown-and-Spectre/m-p/4955#M190</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Hopefully this is the right place to ask a question like this.&lt;/P&gt;&lt;P&gt;Today I looked in the ISC2 Vulnerability Central&amp;nbsp; for the CVSS score for Meltdown and Spectre. To my surprise they scored pretty high. But when I look at NIST NVD they seem to differ. My question is why they differ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;ISC2&lt;/TD&gt;&lt;TD&gt;NVD&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;CVE-2017-5754&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;7.9&lt;/TD&gt;&lt;TD&gt;5.6&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;CVE-2017-5753&lt;/TD&gt;&lt;TD&gt;8.2&lt;/TD&gt;&lt;TD&gt;ongoing&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;CVE-2017-5715&lt;/TD&gt;&lt;TD&gt;8.2&lt;/TD&gt;&lt;TD&gt;5.6&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Roger&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jan 2018 06:51:35 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/CVSS-rating-for-Meltdown-and-Spectre/m-p/4955#M190</guid>
      <dc:creator>re</dc:creator>
      <dc:date>2018-01-08T06:51:35Z</dc:date>
    </item>
    <item>
      <title>Re: CVSS rating for Meltdown and Spectre</title>
      <link>https://community.isc2.org/t5/Tech-Talk/CVSS-rating-for-Meltdown-and-Spectre/m-p/4956#M191</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Nor sure, but I suspect that as ISC2 is using&amp;nbsp;&lt;A href="https://www.cytenna.com/technology.html" target="_self"&gt;https://www.cytenna.com/technology.html&lt;/A&gt;&amp;nbsp;then the score are different because the NVD is scoring in a certain way and Cytenna&amp;nbsp;is doing something different.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It would make sense to me that these were higher up the chain even though they will take some smarts to exploit because of the ubiquity, time to patch performance impact of patch etc.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Whoever&amp;nbsp;works at Cytenna&amp;nbsp;can probably explain more/better.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jan 2018 08:08:08 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/CVSS-rating-for-Meltdown-and-Spectre/m-p/4956#M191</guid>
      <dc:creator>Early_Adopter</dc:creator>
      <dc:date>2018-01-08T08:08:08Z</dc:date>
    </item>
    <item>
      <title>Re: CVSS rating for Meltdown and Spectre</title>
      <link>https://community.isc2.org/t5/Tech-Talk/CVSS-rating-for-Meltdown-and-Spectre/m-p/4964#M192</link>
      <description>&lt;P&gt;As far as I can see, for&amp;nbsp;&lt;SPAN&gt;CVE-2017-5754&lt;/SPAN&gt; the differences come down to the following:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Attack Complexity (Low vs High)&lt;/LI&gt;&lt;LI&gt;Privileges Required (None vs Low)&lt;/LI&gt;&lt;LI&gt;Integrity (Low vs None)&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;From my personal opinion, as far a privileges required, I'd probably go for "none", as attacks can be carried out on a drive-by basis via JavaScript. I'm not entirely sure I'd consider integrity to be none either, given the exposure of secrets and keys could result in an indirect impact on integrity.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jan 2018 09:40:30 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/CVSS-rating-for-Meltdown-and-Spectre/m-p/4964#M192</guid>
      <dc:creator>Graham_Murphy</dc:creator>
      <dc:date>2018-01-08T09:40:30Z</dc:date>
    </item>
    <item>
      <title>Re: CVSS rating for Meltdown and Spectre</title>
      <link>https://community.isc2.org/t5/Tech-Talk/CVSS-rating-for-Meltdown-and-Spectre/m-p/4972#M193</link>
      <description>The risk against integrity is a secondary risk and, with the same logic, availability risk should also be none-zero. Because with the right password recovered it's also possible to shut down services or do other nasty stuff. I am not sure you should take into account these secondary risks when scoring CVSS because confidentiality risks would mostly imply risks to I &amp;amp; A, so for clarity is better to only score the primary risks?</description>
      <pubDate>Mon, 08 Jan 2018 10:45:22 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/CVSS-rating-for-Meltdown-and-Spectre/m-p/4972#M193</guid>
      <dc:creator>Ewald</dc:creator>
      <dc:date>2018-01-08T10:45:22Z</dc:date>
    </item>
    <item>
      <title>Re: CVSS rating for Meltdown and Spectre</title>
      <link>https://community.isc2.org/t5/Tech-Talk/CVSS-rating-for-Meltdown-and-Spectre/m-p/4973#M194</link>
      <description>&lt;P&gt;That's a good point. I had tried to think of similar hardware issues that affect all software, and the closest I could think of was&amp;nbsp;Rowhammer. I tried to dig up how it was scored,(I think CVE-2015-0565) but I haven't be able to find details.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jan 2018 10:54:00 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/CVSS-rating-for-Meltdown-and-Spectre/m-p/4973#M194</guid>
      <dc:creator>Graham_Murphy</dc:creator>
      <dc:date>2018-01-08T10:54:00Z</dc:date>
    </item>
    <item>
      <title>Re: CVSS rating for Meltdown and Spectre</title>
      <link>https://community.isc2.org/t5/Tech-Talk/CVSS-rating-for-Meltdown-and-Spectre/m-p/5009#M195</link>
      <description>&lt;P&gt;For an overview of Meltdown and Spectre, I recommend watching the following video from&lt;/P&gt;&lt;P&gt;SANS Digital Forensics and Incident Response: &lt;A href="https://www.youtube.com/watch?v=8FFSQwrLsfE" target="_blank"&gt;&lt;FONT color="#0066cc"&gt;https://www.youtube.com/watch?v=8FFSQwrLsfE&lt;/FONT&gt;&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jan 2018 14:29:47 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/CVSS-rating-for-Meltdown-and-Spectre/m-p/5009#M195</guid>
      <dc:creator>Nothwindtrader</dc:creator>
      <dc:date>2018-01-08T14:29:47Z</dc:date>
    </item>
  </channel>
</rss>

