<?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 Log4j batch file  execution in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/log4j-batch-file-execution/m-p/456639#M1413</link>
    <description>&lt;P&gt;Hi All.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;From the Palo alto advisory as per below, we have to run a batch file via our SCCM tool. But I need to understand what version of log4j we are using on our Cortex. How can we find out , Please help&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;To ensure you disable message lookup, follow the following steps&lt;/STRONG&gt;:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;STRONG&gt;Disable Log4j &lt;/STRONG&gt;&lt;STRONG&gt;message lookups environment variable&lt;/STRONG&gt;&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;XDR Pro customers&lt;/STRONG&gt; - From the &lt;STRONG&gt;Action Center&lt;/STRONG&gt;, select &lt;STRONG&gt;Actions&lt;/STRONG&gt; &amp;gt; &lt;STRONG&gt;Run Endpoint Script&lt;/STRONG&gt; and in the&lt;STRONG&gt; SCRIPT&lt;/STRONG&gt; field select&lt;STRONG&gt; execute_command&lt;/STRONG&gt;. Specify the &lt;STRONG&gt;Commands_lists(list)&lt;/STRONG&gt; field as &lt;STRONG&gt;setx LOG4J_FORMAT_MSG_NO_LOOKUPS true /M&lt;/STRONG&gt;. In the next screen, you will have an option to select the target machines.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;XDR Prevent customers&lt;/STRONG&gt; - Execute the following batch script with administrative privileges on your machines: &lt;A href="https://u18414439.ct.sendgrid.net/ls/click?upn=5FITEUMzDMkXYQ5uKAwx-2F3vAthcLYPwU8Y7N8kmjkCOg4qgtt4iaSbBH8dHey5E421hSytD6W0fWaRK7VQBxNo4xqZSz9G-2BL-2FVJK6ESqHCv8H9NNM88uZZiQ4SUrKwReZ-rl_On1sYiza99CExn8i2GCURXG0ZSVSQySCPmraPuSI38mUFnDNdPQ0yTQyg8FgIbuXD4atP5gpeGebUyLRh01DjDlg8lBIdBcsg7OzWmtIKl6VpSnuUP23RG6tvw4-2BTmsnfM6b9U9-2BDI0Ioi5blMv0FKcpoaUVlF1xtfouyUelhAHiePhVqFimMBRZi5o2v8-2FoxWdkBtp-2BpLfCKZnC5j9r-2F0NEAlojCHpcOZlsh4K1gv24-2FMDIiDy41AEpivGc2-2B6Bh-2BJqpKWXNI5fG9r98U2xRQ-3D-3D" target="_blank"&gt;https://storage.cloud.google.com/panwxdr-staticfiles/apply_log4shell_workaround.bat&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/OL&gt;</description>
    <pubDate>Tue, 04 Jan 2022 09:42:09 GMT</pubDate>
    <dc:creator>AsifSid</dc:creator>
    <dc:date>2022-01-04T09:42:09Z</dc:date>
    <item>
      <title>Log4j batch file  execution</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/log4j-batch-file-execution/m-p/456639#M1413</link>
      <description>&lt;P&gt;Hi All.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;From the Palo alto advisory as per below, we have to run a batch file via our SCCM tool. But I need to understand what version of log4j we are using on our Cortex. How can we find out , Please help&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;To ensure you disable message lookup, follow the following steps&lt;/STRONG&gt;:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;STRONG&gt;Disable Log4j &lt;/STRONG&gt;&lt;STRONG&gt;message lookups environment variable&lt;/STRONG&gt;&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;XDR Pro customers&lt;/STRONG&gt; - From the &lt;STRONG&gt;Action Center&lt;/STRONG&gt;, select &lt;STRONG&gt;Actions&lt;/STRONG&gt; &amp;gt; &lt;STRONG&gt;Run Endpoint Script&lt;/STRONG&gt; and in the&lt;STRONG&gt; SCRIPT&lt;/STRONG&gt; field select&lt;STRONG&gt; execute_command&lt;/STRONG&gt;. Specify the &lt;STRONG&gt;Commands_lists(list)&lt;/STRONG&gt; field as &lt;STRONG&gt;setx LOG4J_FORMAT_MSG_NO_LOOKUPS true /M&lt;/STRONG&gt;. In the next screen, you will have an option to select the target machines.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;XDR Prevent customers&lt;/STRONG&gt; - Execute the following batch script with administrative privileges on your machines: &lt;A href="https://u18414439.ct.sendgrid.net/ls/click?upn=5FITEUMzDMkXYQ5uKAwx-2F3vAthcLYPwU8Y7N8kmjkCOg4qgtt4iaSbBH8dHey5E421hSytD6W0fWaRK7VQBxNo4xqZSz9G-2BL-2FVJK6ESqHCv8H9NNM88uZZiQ4SUrKwReZ-rl_On1sYiza99CExn8i2GCURXG0ZSVSQySCPmraPuSI38mUFnDNdPQ0yTQyg8FgIbuXD4atP5gpeGebUyLRh01DjDlg8lBIdBcsg7OzWmtIKl6VpSnuUP23RG6tvw4-2BTmsnfM6b9U9-2BDI0Ioi5blMv0FKcpoaUVlF1xtfouyUelhAHiePhVqFimMBRZi5o2v8-2FoxWdkBtp-2BpLfCKZnC5j9r-2F0NEAlojCHpcOZlsh4K1gv24-2FMDIiDy41AEpivGc2-2B6Bh-2BJqpKWXNI5fG9r98U2xRQ-3D-3D" target="_blank"&gt;https://storage.cloud.google.com/panwxdr-staticfiles/apply_log4shell_workaround.bat&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/OL&gt;</description>
      <pubDate>Tue, 04 Jan 2022 09:42:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/log4j-batch-file-execution/m-p/456639#M1413</guid>
      <dc:creator>AsifSid</dc:creator>
      <dc:date>2022-01-04T09:42:09Z</dc:date>
    </item>
    <item>
      <title>Re: Log4j batch file  execution</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/log4j-batch-file-execution/m-p/456858#M1414</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/87372"&gt;@AsifSid&lt;/a&gt;&amp;nbsp;, You're the best person to know what is running in your environments. You can run a XQL query to partially identify if the vulnerable JAR's are being loaded or if JNDI calls are being made in your estate.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This should get you started on the right track:&amp;nbsp;&lt;A href="https://www.paloaltonetworks.com/blog/security-operations/hunting-for-log4j-cve-2021-44228-log4shell-exploit-activity/" target="_blank"&gt;https://www.paloaltonetworks.com/blog/security-operations/hunting-for-log4j-cve-2021-44228-log4shell-exploit-activity/&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jan 2022 03:15:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/log4j-batch-file-execution/m-p/456858#M1414</guid>
      <dc:creator>bbarmanroy</dc:creator>
      <dc:date>2022-01-05T03:15:05Z</dc:date>
    </item>
    <item>
      <title>Re: Log4j batch file  execution</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/log4j-batch-file-execution/m-p/457042#M1417</link>
      <description>&lt;P&gt;The link asks us to log into a google account. We're a Microsoft shop, is there anywhere else we can download the file from?&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jan 2022 18:41:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/log4j-batch-file-execution/m-p/457042#M1417</guid>
      <dc:creator>Victor1</dc:creator>
      <dc:date>2022-01-05T18:41:28Z</dc:date>
    </item>
    <item>
      <title>Re: Log4j batch file  execution</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/log4j-batch-file-execution/m-p/457421#M1422</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/91468"&gt;@Victor1&lt;/a&gt;&amp;nbsp;It is&amp;nbsp;a publicly available link. Are you able to view the link from your mobile or another device?&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jan 2022 02:34:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/log4j-batch-file-execution/m-p/457421#M1422</guid>
      <dc:creator>bbarmanroy</dc:creator>
      <dc:date>2022-01-07T02:34:57Z</dc:date>
    </item>
  </channel>
</rss>

