<?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 CVE-2025-0133 threat 510003 and 510004 detection testing  ? in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/cve-2025-0133-threat-510003-and-510004-detection-testing/m-p/1234141#M6910</link>
    <description>&lt;P&gt;PAN state that as workaround/mitigation - block attacks for this vulnerability by enabling Threat ID 510003 and 510004 ( content v 8995 and that&amp;nbsp; "it is crucial to ensure that Vulnerability Protection profiles are explicitly applied to the security rules that process traffic &lt;STRONG&gt;FROM&lt;/STRONG&gt; GlobalProtect interfaces." I wonder if anyone has managed to validate this threat detection/blocking on a test GP portal ? Of course, it may be that 1. having the SSL-VPN disabled and 2. setting the portal login page set to "none" means this vulnerability is just not exposed. However the Sec Advisory does not state these as workarounds. If sufficient these would appear to be a more straightforward intervention than creating rules to apply vulnerability profiles from the GP portal. However having already gone the extra mile, any advise on testing these threats would be gratefully received.&lt;/P&gt;</description>
    <pubDate>Wed, 16 Jul 2025 16:08:48 GMT</pubDate>
    <dc:creator>LeeFrancis2</dc:creator>
    <dc:date>2025-07-16T16:08:48Z</dc:date>
    <item>
      <title>CVE-2025-0133 threat 510003 and 510004 detection testing  ?</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/cve-2025-0133-threat-510003-and-510004-detection-testing/m-p/1234141#M6910</link>
      <description>&lt;P&gt;PAN state that as workaround/mitigation - block attacks for this vulnerability by enabling Threat ID 510003 and 510004 ( content v 8995 and that&amp;nbsp; "it is crucial to ensure that Vulnerability Protection profiles are explicitly applied to the security rules that process traffic &lt;STRONG&gt;FROM&lt;/STRONG&gt; GlobalProtect interfaces." I wonder if anyone has managed to validate this threat detection/blocking on a test GP portal ? Of course, it may be that 1. having the SSL-VPN disabled and 2. setting the portal login page set to "none" means this vulnerability is just not exposed. However the Sec Advisory does not state these as workarounds. If sufficient these would appear to be a more straightforward intervention than creating rules to apply vulnerability profiles from the GP portal. However having already gone the extra mile, any advise on testing these threats would be gratefully received.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Jul 2025 16:08:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/cve-2025-0133-threat-510003-and-510004-detection-testing/m-p/1234141#M6910</guid>
      <dc:creator>LeeFrancis2</dc:creator>
      <dc:date>2025-07-16T16:08:48Z</dc:date>
    </item>
  </channel>
</rss>

