<?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 out of date CVEs in Advanced Threat Prevention Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/out-of-date-cves/m-p/557984#M2002</link>
    <description>&lt;P&gt;I am curious about the listing of vulnerabilities in the vulnerabilities assessment.&amp;nbsp; It seems like it is catching old out dated CVE's and attaching them to fully updated machines.&amp;nbsp; for example i have numerous machines showing a vulnerability CVE-2023-21812, which is updated via update kb5025022899 but that update is superseded by update kb5023765 which my machines have.&amp;nbsp; That update should render that CVE as remediated and not attach it to the machine.&amp;nbsp; i have so many examples of this and i feel like it makes vulnerability assessment a useless tool.&amp;nbsp; I have read that we can exempt certain CVEs from appearing in our search, however what happens if i actually have a machine that is vulnerable to that CVE.&amp;nbsp; Is there a way to filter out these CVEs from machines that are already updated.&lt;/P&gt;</description>
    <pubDate>Thu, 14 Sep 2023 18:21:54 GMT</pubDate>
    <dc:creator>JonasR2023</dc:creator>
    <dc:date>2023-09-14T18:21:54Z</dc:date>
    <item>
      <title>out of date CVEs</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/out-of-date-cves/m-p/557984#M2002</link>
      <description>&lt;P&gt;I am curious about the listing of vulnerabilities in the vulnerabilities assessment.&amp;nbsp; It seems like it is catching old out dated CVE's and attaching them to fully updated machines.&amp;nbsp; for example i have numerous machines showing a vulnerability CVE-2023-21812, which is updated via update kb5025022899 but that update is superseded by update kb5023765 which my machines have.&amp;nbsp; That update should render that CVE as remediated and not attach it to the machine.&amp;nbsp; i have so many examples of this and i feel like it makes vulnerability assessment a useless tool.&amp;nbsp; I have read that we can exempt certain CVEs from appearing in our search, however what happens if i actually have a machine that is vulnerable to that CVE.&amp;nbsp; Is there a way to filter out these CVEs from machines that are already updated.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Sep 2023 18:21:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/out-of-date-cves/m-p/557984#M2002</guid>
      <dc:creator>JonasR2023</dc:creator>
      <dc:date>2023-09-14T18:21:54Z</dc:date>
    </item>
  </channel>
</rss>

