<?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: Is Palo vulnerable to the shell shock Linux bug? in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25150#M18350</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;PAN-OS includes bash, which means it is likely vulnerable:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;test-box&amp;gt; debug cli detail &lt;/P&gt;&lt;P&gt;Environment variables :&lt;/P&gt;&lt;P&gt;(LANG . en_US.UTF-8)&lt;/P&gt;&lt;P&gt;(USER . admin)&lt;/P&gt;&lt;P&gt;(LOGNAME . admin)&lt;/P&gt;&lt;P&gt;(HOME . /opt/pancfg/home/admin)&lt;/P&gt;&lt;P&gt;(PATH . /usr/local/bin:/bin:/usr/bin)&lt;/P&gt;&lt;P&gt;(MAIL . /var/mail/admin)&lt;/P&gt;&lt;P&gt;(SHELL . /bin/bash)&lt;/P&gt;&lt;P&gt;(SSH_CLIENT . 192.0.2.1 57409 22)&lt;/P&gt;&lt;P&gt;(SSH_CONNECTION . 192.0.2.1 57409 192.0.2.2 22)&lt;/P&gt;&lt;P&gt;(SSH_TTY . /dev/pts/0)&lt;/P&gt;&lt;P&gt;(TERM . xterm)&lt;/P&gt;&lt;P&gt;(SSH_AUTH_SOCK . /tmp/ssh-vHZslV9235/agent.9235)&lt;/P&gt;&lt;P&gt;(LESSCHARSET . utf-8)&lt;/P&gt;&lt;P&gt;(PAN_BASE_DIR . /opt/pancfg/mgmt)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Build Target : panos-5000-mp&lt;/P&gt;&lt;P&gt;Build Type&amp;nbsp;&amp;nbsp; : RELEASE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Total Heap : 7.16 M&lt;/P&gt;&lt;P&gt;Used&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 6.11 M&lt;/P&gt;&lt;P&gt;Nursery&amp;nbsp;&amp;nbsp;&amp;nbsp; : 0.12 M&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 25 Sep 2014 17:07:27 GMT</pubDate>
    <dc:creator>rvandegrift</dc:creator>
    <dc:date>2014-09-25T17:07:27Z</dc:date>
    <item>
      <title>Is Palo vulnerable to the shell shock Linux bug?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25138#M18338</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is Palo vulnerable to the shell shock Linux bug?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.theregister.co.uk/2014/09/24/bash_shell_vuln/" style="font-size: 10pt; line-height: 1.5em;" title="http://www.theregister.co.uk/2014/09/24/bash_shell_vuln/"&gt;http://www.theregister.co.uk/2014/09/24/bash_shell_vuln/&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Sep 2014 12:12:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25138#M18338</guid>
      <dc:creator>Smi12</dc:creator>
      <dc:date>2014-09-25T12:12:26Z</dc:date>
    </item>
    <item>
      <title>Re: Is Palo vulnerable to the shell shock Linux bug?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25139#M18339</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I also wonder if it is or not&lt;/P&gt;&lt;P&gt;There are some fixes and tests on the web for linux and macos but we don't have root access to test &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://live.paloaltonetworks.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Sep 2014 12:35:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25139#M18339</guid>
      <dc:creator>Retired Member</dc:creator>
      <dc:date>2014-09-25T12:35:37Z</dc:date>
    </item>
    <item>
      <title>Re: Is Palo vulnerable to the shell shock Linux bug?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25140#M18340</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I believe the latest emergency content update addresses this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;H1 style="color: #222222; font-family: arial, sans-serif;"&gt;Application and Threat Content Release Notes&lt;/H1&gt;&lt;H2 style="color: #222222; font-family: arial, sans-serif;"&gt;Version 457&lt;/H2&gt;&lt;P&gt;&lt;STRONG style="color: #222222; font-family: arial, sans-serif;"&gt;Notes&lt;/STRONG&gt;&lt;SPAN style="color: #222222; font-family: arial, sans-serif;"&gt;: Earlier today, Wednesday, September 24th, Palo Alto Networks became aware of a remote code execution vulnerability in the Bash shell utility. This vulnerability is CVE-2014-6271 and allows for remote code execution through multiple vectors due to the way Bash is often used on linux systems for processing commands. Additional information can be found here: &lt;/SPAN&gt;&lt;A href="http://seclists.org/oss-sec/2014/q3/650" style="color: #1155cc; font-family: arial, sans-serif;" target="_blank"&gt;http://seclists.org/oss-sec/2014/q3/650&lt;/A&gt;&lt;/P&gt;&lt;P style="color: #222222; font-family: arial, sans-serif;"&gt;To address this vulnerability, Palo Alto Networks has released an emergency content update that provides detection of attempted exploitation of CVE-2014-6271 with IPS vulnerability Signature ID: 36729 "Bash Remote Code Execution Vulnerability" with Critical severity and default action of "Alert." Palo Alto Networks customers with a Threat Prevention subscription are advised to verify that they are running the latest content version on their devices. If you have any questions about coverage for this advisory, please contact Support.&lt;/P&gt;&lt;H3 style="color: #222222; font-family: arial, sans-serif;"&gt;New Vulnerability Signatures (1)&lt;/H3&gt;&lt;TABLE style="color: #222222; font-family: arial, sans-serif;"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TH width="71"&gt;Severity&lt;/TH&gt;&lt;TH width="71"&gt;ID&lt;/TH&gt;&lt;TH&gt;Attack Name&lt;/TH&gt;&lt;TH width="105"&gt;CVE ID&lt;/TH&gt;&lt;TH width="80"&gt;Vendor ID&lt;/TH&gt;&lt;TH width="18%"&gt;Default Action&lt;/TH&gt;&lt;TH width="18%"&gt;Minimum PAN-OS Version&lt;/TH&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;critical&lt;/TD&gt;&lt;TD&gt;36729&lt;/TD&gt;&lt;TD&gt;Bash Remote Code Execution Vulnerability&lt;/TD&gt;&lt;TD&gt;CVE-2014-6271&lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;alert&lt;/TD&gt;&lt;TD&gt;4.0.0&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Sep 2014 12:38:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25140#M18340</guid>
      <dc:creator>mrsoldner</dc:creator>
      <dc:date>2014-09-25T12:38:38Z</dc:date>
    </item>
    <item>
      <title>Re: Is Palo vulnerable to the shell shock Linux bug?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25141#M18341</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello &lt;STRONG style="font-size: 12px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3b3b3b;"&gt;&lt;A _jive_internal="true" class="jiveTT-hover-user jive-username-link" data-avatarid="1252" data-externalid="" data-presence="null" data-userid="23067" data-username="Smi12" href="https://live.paloaltonetworks.com/people/Smi12" style="padding: 0 3px 0 0; font-weight: inherit; font-style: inherit; font-size: 1.1em; font-family: inherit; color: #006595;"&gt;Smi12&lt;/A&gt;&lt;/STRONG&gt;,&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt; font-family: 'Calibri','sans-serif'; color: #1f497d;"&gt;Content update 457-2377 with coverage for CVE-2014-6271&lt;/SPAN&gt;&lt;SPAN style="font-size: 11.0pt; font-family: 'Calibri','sans-serif';"&gt; &lt;SPAN style="color: #1f497d;"&gt;Signature ID: 36729 "Bash Remote Code Execution Vulnerability" has been released&lt;SPAN class="GINGER_SOFTWARE_mark"&gt; .&lt;/SPAN&gt; Please update the PAN firewall with latest Application and Threat database.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d; font-size: 11.0pt; font-family: 'Calibri','sans-serif';"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d; font-size: 11.0pt; font-family: 'Calibri','sans-serif';"&gt;Thanks&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Sep 2014 12:38:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25141#M18341</guid>
      <dc:creator>HULK</dc:creator>
      <dc:date>2014-09-25T12:38:39Z</dc:date>
    </item>
    <item>
      <title>Re: Is Palo vulnerable to the shell shock Linux bug?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25142#M18342</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;FYI..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG __jive_id="15788" alt="emergency-content-release.jpg" class="image-1 jive-image" height="84" src="https://live.paloaltonetworks.com/legacyfs/online/15788_emergency-content-release.jpg" style="height: 84px; width: 1680px;" width="1680" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Sep 2014 12:42:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25142#M18342</guid>
      <dc:creator>HULK</dc:creator>
      <dc:date>2014-09-25T12:42:25Z</dc:date>
    </item>
    <item>
      <title>Re: Is Palo vulnerable to the shell shock Linux bug?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25143#M18343</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Good to know that there is a signature for it, but it doesn't answer the question if the OS itself is vulnerable of not&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Bob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Sep 2014 12:56:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25143#M18343</guid>
      <dc:creator>${userLoginName}</dc:creator>
      <dc:date>2014-09-25T12:56:27Z</dc:date>
    </item>
    <item>
      <title>Re: Is Palo vulnerable to the shell shock Linux bug?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25144#M18344</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I agree with bdeschut...What's the story with that?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Sep 2014 13:18:12 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25144#M18344</guid>
      <dc:creator>chrisp</dc:creator>
      <dc:date>2014-09-25T13:18:12Z</dc:date>
    </item>
    <item>
      <title>Re: Is Palo vulnerable to the shell shock Linux bug?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25145#M18345</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;yes that was the real question I think&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Sep 2014 13:20:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25145#M18345</guid>
      <dc:creator>Retired Member</dc:creator>
      <dc:date>2014-09-25T13:20:53Z</dc:date>
    </item>
    <item>
      <title>Re: Is Palo vulnerable to the shell shock Linux bug?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25146#M18346</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Still trying to work out if the Linux based PAN-OS including that used by Panorama is vulnerable to this also?&amp;nbsp; any thoughts &lt;A href="https://live.paloaltonetworks.com/u1/19491"&gt;HULK&lt;/A&gt; or&amp;nbsp; &lt;A href="https://live.paloaltonetworks.com/u1/21363"&gt;mrsoldner&lt;/A&gt; ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Sep 2014 14:35:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25146#M18346</guid>
      <dc:creator>Smi12</dc:creator>
      <dc:date>2014-09-25T14:35:55Z</dc:date>
    </item>
    <item>
      <title>Re: Is Palo vulnerable to the shell shock Linux bug?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25147#M18347</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It is...&lt;A href="https://securityadvisories.paloaltonetworks.com/" title="https://securityadvisories.paloaltonetworks.com/"&gt;Palo Alto Networks Product Vulnerability - Security Advisories&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;They have it as a LOW.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Sep 2014 14:43:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25147#M18347</guid>
      <dc:creator>chrisp</dc:creator>
      <dc:date>2014-09-25T14:43:03Z</dc:date>
    </item>
    <item>
      <title>Re: Is Palo vulnerable to the shell shock Linux bug?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25148#M18348</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Default Action on the signature is set to alert, which is very strange for something that could potentially be used to create DHCP worms across virtually every non-Windows platform, including smartphones.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We've installed the update onto all our PANOS boxes, but cannot see ID 36729 nor the CVE number appear in the signatures list. Regardless of that, if I create a rule to match the 36729 ID with block as the action will the device take it?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Sep 2014 14:46:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25148#M18348</guid>
      <dc:creator>David_Hulse</dc:creator>
      <dc:date>2014-09-25T14:46:24Z</dc:date>
    </item>
    <item>
      <title>Re: Is Palo vulnerable to the shell shock Linux bug?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25149#M18349</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;
&lt;P&gt;dynamicv wrote:&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Default Action on the signature is set to alert, which is very strange for something that could potentially be used to create DHCP worms across virtually every non-Windows platform, including smartphones. &lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;We've installed the update onto all our PANOS boxes, but cannot see ID 36729 nor the CVE number appear in the signatures list. Regardless of that, if I create a rule to match the 36729 ID with block as the action will the device take it?&lt;/P&gt;
&lt;/PRE&gt;&lt;P&gt;You can make an exception and change the default action. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Go into your Vulnerability Protection Profile&lt;/LI&gt;&lt;LI&gt;Click "Exceptions"&lt;/LI&gt;&lt;LI&gt;Check "Show all signatures"&lt;/LI&gt;&lt;LI&gt;Enter 36729&lt;/LI&gt;&lt;LI&gt;Change the action to whatever you'd like it to be.&lt;/LI&gt;&lt;LI&gt;Push policy.&lt;/LI&gt;&lt;/OL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Sep 2014 15:41:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25149#M18349</guid>
      <dc:creator>mrsoldner</dc:creator>
      <dc:date>2014-09-25T15:41:55Z</dc:date>
    </item>
    <item>
      <title>Re: Is Palo vulnerable to the shell shock Linux bug?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25150#M18350</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;PAN-OS includes bash, which means it is likely vulnerable:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;test-box&amp;gt; debug cli detail &lt;/P&gt;&lt;P&gt;Environment variables :&lt;/P&gt;&lt;P&gt;(LANG . en_US.UTF-8)&lt;/P&gt;&lt;P&gt;(USER . admin)&lt;/P&gt;&lt;P&gt;(LOGNAME . admin)&lt;/P&gt;&lt;P&gt;(HOME . /opt/pancfg/home/admin)&lt;/P&gt;&lt;P&gt;(PATH . /usr/local/bin:/bin:/usr/bin)&lt;/P&gt;&lt;P&gt;(MAIL . /var/mail/admin)&lt;/P&gt;&lt;P&gt;(SHELL . /bin/bash)&lt;/P&gt;&lt;P&gt;(SSH_CLIENT . 192.0.2.1 57409 22)&lt;/P&gt;&lt;P&gt;(SSH_CONNECTION . 192.0.2.1 57409 192.0.2.2 22)&lt;/P&gt;&lt;P&gt;(SSH_TTY . /dev/pts/0)&lt;/P&gt;&lt;P&gt;(TERM . xterm)&lt;/P&gt;&lt;P&gt;(SSH_AUTH_SOCK . /tmp/ssh-vHZslV9235/agent.9235)&lt;/P&gt;&lt;P&gt;(LESSCHARSET . utf-8)&lt;/P&gt;&lt;P&gt;(PAN_BASE_DIR . /opt/pancfg/mgmt)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Build Target : panos-5000-mp&lt;/P&gt;&lt;P&gt;Build Type&amp;nbsp;&amp;nbsp; : RELEASE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Total Heap : 7.16 M&lt;/P&gt;&lt;P&gt;Used&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 6.11 M&lt;/P&gt;&lt;P&gt;Nursery&amp;nbsp;&amp;nbsp;&amp;nbsp; : 0.12 M&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Sep 2014 17:07:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25150#M18350</guid>
      <dc:creator>rvandegrift</dc:creator>
      <dc:date>2014-09-25T17:07:27Z</dc:date>
    </item>
    <item>
      <title>Re: Is Palo vulnerable to the shell shock Linux bug?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25151#M18351</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"Low" vulnerability to PAN-OS is premised on only authenticated users being able to exploit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But elsewhere I've seen reports that the vulnerability doesn't require authentication to exploit. Based on &lt;A href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-6271" title="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-6271"&gt;NVD - Detail&lt;/A&gt; it seems PAN-OS could (emphasize could) be vulnerable either through ssh or the web interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, like dynamicv, I can't see the signature in the update even when I follow mrsoldner's instructions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EDIT: Some time after the above, I updated PAN-OS from 6.0.4. to 6.0.5, and rebooted the firewall as part of the update. The signature is visible now.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Sep 2014 17:46:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25151#M18351</guid>
      <dc:creator>Elliot_Wilen</dc:creator>
      <dc:date>2014-09-25T17:46:52Z</dc:date>
    </item>
    <item>
      <title>Re: Is Palo vulnerable to the shell shock Linux bug?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25152#M18352</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;Per product management, &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;"The Bash vulnerability currently appears to be a low severity issue due to the fact that only authenticated users could potentially exploit the vulnerability against PAN-OS.&amp;nbsp; Normal PAN-OS maintenance release updates will provide a fix for the vulnerability." &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, there is an internal bug open where the bash patch will be applied in the PAN-OS (it is yet to be confirmed in which release will the fix be available and whether it will be backported to the previous releases) Hope this helps. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 27 Sep 2014 03:01:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25152#M18352</guid>
      <dc:creator>gchandrasekaran</dc:creator>
      <dc:date>2014-09-27T03:01:54Z</dc:date>
    </item>
    <item>
      <title>Re: Is Palo vulnerable to the shell shock Linux bug?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25153#M18353</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please note our new release.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Version 458&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Notes&lt;/STRONG&gt;: Release notes for emergency content release for CVE-2014-6271 update and CVE-2014-7169&lt;/P&gt;&lt;P&gt;Thursday, September 25th, Palo Alto Networks became aware of additional vulnerabilities with the Bash shell utility. The fixes for CVE-2014-6271 were incomplete from Operating System vendors and there is a new vulnerability, CVE-2014-7169, that describes this issue. To address this new vulnerability, Palo Alto Networks is releasing an emergency content update that provides updated detection of both CVE-2014-7169 and the previous CVE-2014-6271 vulnerability with an update to the IPS vulnerability Signature ID: 36729 "Bash Remote Code Execution Vulnerability" with "Critical" severity and default action of "Alert". &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please don't forget to mark this discussion as answered if we have addressed your concerns. &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://live.paloaltonetworks.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Sep 2014 22:47:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/is-palo-vulnerable-to-the-shell-shock-linux-bug/m-p/25153#M18353</guid>
      <dc:creator>mmmccorkle</dc:creator>
      <dc:date>2014-09-30T22:47:38Z</dc:date>
    </item>
  </channel>
</rss>

