About ymiyashita

I would suggest to find the sample which is being blocked by the signature and check the verdict (you can upload it to the WildFire cloud to see the verdict). If it's benign, you can set an exception to allow the file temporarily as needed. It is called 'signature collision'. The signature was created for a bunch of malware samples. We should keep the signature enabled instead of disabling it. https://threatvault.paloaltonetworks.com/?query=479496371&type=   References: - Manually Upload Files to the WildFire Portal https://docs.paloaltonetworks.com/wildfire/9-1/wildfire-admin/submit-files-for-wildfire-analysis/manually-upload-files-to-the-wildfire-portal - What is an Antivirus collision in the case of a False Positive, and how can we deal with it? https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClWICA0 - How to Use Anti-Spyware, Vulnerability and Antivirus Exceptions to Block or Allow Threats https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClcrCAC       ... View more

PA firewall is not the one which is affected. Palo Alto Networks released a signature (TID: 93319) to mitigate the issue in the Microsoft Exchange Server (CVE-2022-41080).   Reference: https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2022-41080   ... View more

Both PAN-202288 and PAN-206672 do not appear to be related to "Threat & Vulnerability". You may want to post it to "General Topics" or open a support case with Palo Alto Networks. ... View more

A signature was already released. It's a vulnerability protection signature (not an AV signature). https://threatvault.paloaltonetworks.com/?query=CVE-2022-2884&type=   Palo Alto Networks Firewall is not using GitLab, thus not affected by CVE-2022-2884. ... View more