<?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: CVE-2023-38802 Dynamic Update Signature in Custom Signatures</title>
    <link>https://live.paloaltonetworks.com/t5/custom-signatures/cve-2023-38802-dynamic-update-signature/m-p/560993#M482</link>
    <description>&lt;P&gt;The signature for CVE-2023-38802 was already released on 2023-10-03 UTC.&lt;BR /&gt;&lt;A href="https://threatvault.paloaltonetworks.com/?query=CVE-2023-38802&amp;amp;type=" target="_blank"&gt;https://threatvault.paloaltonetworks.com/?query=CVE-2023-38802&amp;amp;type=&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;# By the way, when you ask about a signature coverage for a new CVE, I'd suggest to use the following place from the next time onwards because this place is for a custom signature.&lt;BR /&gt;&lt;A href="https://live.paloaltonetworks.com/t5/threat-vulnerability-discussions/bd-p/Threat_Discussions" target="_blank"&gt;https://live.paloaltonetworks.com/t5/threat-vulnerability-discussions/bd-p/Threat_Discussions&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 10 Oct 2023 00:55:01 GMT</pubDate>
    <dc:creator>ymiyashita</dc:creator>
    <dc:date>2023-10-10T00:55:01Z</dc:date>
    <item>
      <title>CVE-2023-38802 Dynamic Update Signature</title>
      <link>https://live.paloaltonetworks.com/t5/custom-signatures/cve-2023-38802-dynamic-update-signature/m-p/560799#M481</link>
      <description>&lt;P&gt;Hi Palo Alto Networks Team,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would like to request to add&amp;nbsp;CVE-2023-38802 vulnerability signature to dynamic update.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have a few of client having concern about this signature.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 06 Oct 2023 07:47:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/custom-signatures/cve-2023-38802-dynamic-update-signature/m-p/560799#M481</guid>
      <dc:creator>JiaXiang</dc:creator>
      <dc:date>2023-10-06T07:47:06Z</dc:date>
    </item>
    <item>
      <title>Re: CVE-2023-38802 Dynamic Update Signature</title>
      <link>https://live.paloaltonetworks.com/t5/custom-signatures/cve-2023-38802-dynamic-update-signature/m-p/560993#M482</link>
      <description>&lt;P&gt;The signature for CVE-2023-38802 was already released on 2023-10-03 UTC.&lt;BR /&gt;&lt;A href="https://threatvault.paloaltonetworks.com/?query=CVE-2023-38802&amp;amp;type=" target="_blank"&gt;https://threatvault.paloaltonetworks.com/?query=CVE-2023-38802&amp;amp;type=&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;# By the way, when you ask about a signature coverage for a new CVE, I'd suggest to use the following place from the next time onwards because this place is for a custom signature.&lt;BR /&gt;&lt;A href="https://live.paloaltonetworks.com/t5/threat-vulnerability-discussions/bd-p/Threat_Discussions" target="_blank"&gt;https://live.paloaltonetworks.com/t5/threat-vulnerability-discussions/bd-p/Threat_Discussions&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 10 Oct 2023 00:55:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/custom-signatures/cve-2023-38802-dynamic-update-signature/m-p/560993#M482</guid>
      <dc:creator>ymiyashita</dc:creator>
      <dc:date>2023-10-10T00:55:01Z</dc:date>
    </item>
  </channel>
</rss>

