<?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 Detect any ELF executable in Custom Signatures</title>
    <link>https://live.paloaltonetworks.com/t5/custom-signatures/detect-any-elf-executable/m-p/101267#M117</link>
    <description>&lt;P&gt;I would like to block any ELF executable, but this is not support in file blocking. I have tried to achieve this using two methods:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Create a custom data pattern. This didn't really work out, as the minimum string length is 7 bytes, but the file identifier is only four, plus it needs to be in the start of the file rather than anywhere in the file.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Create a custom vulnerability. This is ok, but not ideal. I created a pattern-match condition, with a context of &lt;STRONG&gt;file-elf-body&lt;/STRONG&gt;. Unfortunately, I then need to add a 7 byte value to match against. I have put &lt;STRONG&gt;\x00000000000000\x&lt;/STRONG&gt;, which catches any file I can find, but it is concievable that there are files with no such string.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can anyone else suggest a better solution to this? You may have guessed, I'm a complete novice at this.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 05 Aug 2016 01:18:38 GMT</pubDate>
    <dc:creator>stephengun</dc:creator>
    <dc:date>2016-08-05T01:18:38Z</dc:date>
    <item>
      <title>Detect any ELF executable</title>
      <link>https://live.paloaltonetworks.com/t5/custom-signatures/detect-any-elf-executable/m-p/101267#M117</link>
      <description>&lt;P&gt;I would like to block any ELF executable, but this is not support in file blocking. I have tried to achieve this using two methods:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Create a custom data pattern. This didn't really work out, as the minimum string length is 7 bytes, but the file identifier is only four, plus it needs to be in the start of the file rather than anywhere in the file.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Create a custom vulnerability. This is ok, but not ideal. I created a pattern-match condition, with a context of &lt;STRONG&gt;file-elf-body&lt;/STRONG&gt;. Unfortunately, I then need to add a 7 byte value to match against. I have put &lt;STRONG&gt;\x00000000000000\x&lt;/STRONG&gt;, which catches any file I can find, but it is concievable that there are files with no such string.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can anyone else suggest a better solution to this? You may have guessed, I'm a complete novice at this.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Aug 2016 01:18:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/custom-signatures/detect-any-elf-executable/m-p/101267#M117</guid>
      <dc:creator>stephengun</dc:creator>
      <dc:date>2016-08-05T01:18:38Z</dc:date>
    </item>
    <item>
      <title>Re: Detect any ELF executable</title>
      <link>https://live.paloaltonetworks.com/t5/custom-signatures/detect-any-elf-executable/m-p/101327#M118</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You could try to do a pattern match on the context "file-unknown-body", with 4 7-byte patterns representing the different classes (32-bit or 64-bit) and endianness (little endian or big endian):&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;\x7f454c46010101\x&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;\x7f454c46010201\x&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;\x7f454c46020101\x&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;\x7f454c46020201\x&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I haven't tried it myself, but I don't see why it wouldn't work.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Benjamin&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Aug 2016 18:28:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/custom-signatures/detect-any-elf-executable/m-p/101327#M118</guid>
      <dc:creator>BenjAudy.MTL</dc:creator>
      <dc:date>2016-08-05T18:28:23Z</dc:date>
    </item>
    <item>
      <title>Re: Detect any ELF executable</title>
      <link>https://live.paloaltonetworks.com/t5/custom-signatures/detect-any-elf-executable/m-p/145833#M155</link>
      <description>&lt;P&gt;It looks like content update 667 added a&amp;nbsp;new file type to detect ELF files (ID #52175).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Benjamin&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2017 15:50:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/custom-signatures/detect-any-elf-executable/m-p/145833#M155</guid>
      <dc:creator>BenjAudy.MTL</dc:creator>
      <dc:date>2017-03-02T15:50:36Z</dc:date>
    </item>
  </channel>
</rss>

