<?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: Vuln Sigs for SQL Injection in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/vuln-sigs-for-sql-injection/m-p/3329#M2484</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class="MsoPlainText"&gt;We were looking couple of patterns:&lt;/P&gt;&lt;P class="MsoPlainText"&gt;&lt;/P&gt;&lt;P class="MsoPlainText"&gt;1) some SQL sentences/keywords which were used for SQL Injection attempt.&lt;/P&gt;&lt;P class="MsoPlainText"&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;like "union select", "select char" something.&lt;/P&gt;&lt;P class="MsoPlainText"&gt;&lt;/P&gt;&lt;P class="MsoPlainText"&gt;2) Some SQL functions which were used for SQL injection evasion.&lt;/P&gt;&lt;P class="MsoPlainText"&gt;&lt;/P&gt;&lt;P class="MsoPlainText"&gt;3) Some SQL "or" conditions which were used for SQL injection probe, like "or 1=1".&lt;/P&gt;&lt;P class="MsoPlainText"&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P class="MsoPlainText"&gt;If customer found those alerts, it might be a probe or from a scanner. It does not means customer's&lt;/P&gt;&lt;P class="MsoPlainText"&gt;server is vulnerable.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 04 Oct 2010 20:56:54 GMT</pubDate>
    <dc:creator>odaos</dc:creator>
    <dc:date>2010-10-04T20:56:54Z</dc:date>
    <item>
      <title>Vuln Sigs for SQL Injection</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/vuln-sigs-for-sql-injection/m-p/3328#M2483</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There are several sigs described as &amp;amp;quot;HTTP SQL Injection&amp;amp;quot; (30514, 33338, 33340, 33305, and maybe others) that are server-side mediums with a default alert. What are these signatures looking for? Atypical SQL statements that indicate an attempt to get more from a database than one might normally need? More info in the description would be helpful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Oct 2010 14:20:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/vuln-sigs-for-sql-injection/m-p/3328#M2483</guid>
      <dc:creator>gmoerschel</dc:creator>
      <dc:date>2010-10-04T14:20:24Z</dc:date>
    </item>
    <item>
      <title>Re: Vuln Sigs for SQL Injection</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/vuln-sigs-for-sql-injection/m-p/3329#M2484</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class="MsoPlainText"&gt;We were looking couple of patterns:&lt;/P&gt;&lt;P class="MsoPlainText"&gt;&lt;/P&gt;&lt;P class="MsoPlainText"&gt;1) some SQL sentences/keywords which were used for SQL Injection attempt.&lt;/P&gt;&lt;P class="MsoPlainText"&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;like "union select", "select char" something.&lt;/P&gt;&lt;P class="MsoPlainText"&gt;&lt;/P&gt;&lt;P class="MsoPlainText"&gt;2) Some SQL functions which were used for SQL injection evasion.&lt;/P&gt;&lt;P class="MsoPlainText"&gt;&lt;/P&gt;&lt;P class="MsoPlainText"&gt;3) Some SQL "or" conditions which were used for SQL injection probe, like "or 1=1".&lt;/P&gt;&lt;P class="MsoPlainText"&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P class="MsoPlainText"&gt;If customer found those alerts, it might be a probe or from a scanner. It does not means customer's&lt;/P&gt;&lt;P class="MsoPlainText"&gt;server is vulnerable.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Oct 2010 20:56:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/vuln-sigs-for-sql-injection/m-p/3329#M2484</guid>
      <dc:creator>odaos</dc:creator>
      <dc:date>2010-10-04T20:56:54Z</dc:date>
    </item>
  </channel>
</rss>

