<?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: Gumblar Bot Net - IPS Signatures in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/gumblar-bot-net-ips-signatures/m-p/1181421#M77045</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;perhaps you need to write a custom signature&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 01 Jun 2009 01:02:44 GMT</pubDate>
    <dc:creator>yuliang13</dc:creator>
    <dc:date>2009-06-01T01:02:44Z</dc:date>
    <item>
      <title>Gumblar Bot Net - IPS Signatures</title>
      <link>https://community.cisco.com/t5/network-security/gumblar-bot-net-ips-signatures/m-p/1181420#M77040</link>
      <description>&lt;P&gt;According to Cisco's bulletin, they do not have any signatures recommended to stop the Gumblar Bot Net.  However, a client of ours, uses IBM's Proventia and they currently have a list of signatures they recommend to block.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IBM: &lt;A class="jive-link-custom" href="http://www.iss.net/threats/gumblar.html" target="_blank"&gt;http://www.iss.net/threats/gumblar.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cisco: &lt;A class="jive-link-custom" href="http://tools.cisco.com/security/center/viewAlert.x?alertId=18286" target="_blank"&gt;http://tools.cisco.com/security/center/viewAlert.x?alertId=18286&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since I'm new to the IPS realm, I'm curious if I can basically set to block all of the PDF related remote execution/vulnerabilities and curious if this will help us in mitigating this attack.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for any guidance you may give.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 11:38:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/gumblar-bot-net-ips-signatures/m-p/1181420#M77040</guid>
      <dc:creator>solinal01</dc:creator>
      <dc:date>2019-03-10T11:38:47Z</dc:date>
    </item>
    <item>
      <title>Re: Gumblar Bot Net - IPS Signatures</title>
      <link>https://community.cisco.com/t5/network-security/gumblar-bot-net-ips-signatures/m-p/1181421#M77045</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;perhaps you need to write a custom signature&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Jun 2009 01:02:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/gumblar-bot-net-ips-signatures/m-p/1181421#M77045</guid>
      <dc:creator>yuliang13</dc:creator>
      <dc:date>2009-06-01T01:02:44Z</dc:date>
    </item>
    <item>
      <title>Re: Gumblar Bot Net - IPS Signatures</title>
      <link>https://community.cisco.com/t5/network-security/gumblar-bot-net-ips-signatures/m-p/1181422#M77048</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well considering I'm new to all of this, I guess that is not going to happen. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Jun 2009 11:16:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/gumblar-bot-net-ips-signatures/m-p/1181422#M77048</guid>
      <dc:creator>solinal01</dc:creator>
      <dc:date>2009-06-01T11:16:48Z</dc:date>
    </item>
    <item>
      <title>Re: Gumblar Bot Net - IPS Signatures</title>
      <link>https://community.cisco.com/t5/network-security/gumblar-bot-net-ips-signatures/m-p/1181423#M77051</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ask, and ye shall receive:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create a custom sig using the service-http engine.  Set it for TCP and use the built-in WEBPORTS variable for common ports (although in the case you can probably do tcp/80.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Specify the Argument Name Regex as:&lt;/P&gt;&lt;P&gt;((action=).*(&amp;amp;entity_list=).*(&amp;amp;uid=).*(&amp;amp;first=).*(&amp;amp;guid=).*(&amp;amp;rnd=).*)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Full disclosure:  this is my first real attempt at using Regex in an IPS sig.  I would assume there are better ways to write this regex; this is just what I came up with.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What the regex is saying is "match exactly on the string "action=" followed by any character (the '.') any number of times (the '*'), followed by the the string (&amp;amp;entity_list=) etc.  They have to be in that exact order.  In this version it has to be a case-sensitive match.  It should really be broken down like: ([Aa][Cc][Tt][Ii][Oo][Nn][=]) but the malware isn't exhibiting that behavior yet, so...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You want to swap the attacker/victim setting to (i.e. even though its an internal host that's initiating the traffic, its really the destination that's the bad guy.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For what its worth, I would think that the Cisco guys should be able to create this as a real sig for inclusion in their updates.  If you guys are interested I can try converting more of the Emerging Threat (emergingthreats.net) sigs to be Cisco IPS sigs.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Jun 2009 18:42:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/gumblar-bot-net-ips-signatures/m-p/1181423#M77051</guid>
      <dc:creator>clausonna</dc:creator>
      <dc:date>2009-06-10T18:42:43Z</dc:date>
    </item>
    <item>
      <title>Re: Gumblar Bot Net - IPS Signatures</title>
      <link>https://community.cisco.com/t5/network-security/gumblar-bot-net-ips-signatures/m-p/1181424#M77054</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sweet - thank you thank you thank you!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unfortunately, I cannot 'test' this, and since this would be my 'first' one, I would like to test before I place into production....our licenses are 'mixed up' for my lab ASA/IPS....as soon as that is ironed out - I will definitely attempt this!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you again!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lillian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Jun 2009 18:47:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/gumblar-bot-net-ips-signatures/m-p/1181424#M77054</guid>
      <dc:creator>solinal01</dc:creator>
      <dc:date>2009-06-10T18:47:36Z</dc:date>
    </item>
    <item>
      <title>Re: Gumblar Bot Net - IPS Signatures</title>
      <link>https://community.cisco.com/t5/network-security/gumblar-bot-net-ips-signatures/m-p/1181425#M77059</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Happy to help.  I strongly recommend testing this sig first, since Regex is CPU intensive (and since, as I mentioned, I'm new to writing Regex sigs).  You could remove some of the 'inside' Arg Names to simplify the regex (ie. get rid of the &amp;amp;first= or &amp;amp;guid= names) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've already had a true positive hit on this sig, from a guest machine on my network.  Here's the HTTP GET that the infected client issued:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;GET /garret/controller.php?action=bot&amp;amp;entity_list=2351576910,1212183482,1232434&amp;amp;uid=1&amp;amp;first=0&amp;amp;guid=22439923423&amp;amp;rnd=9242 HTTP/1.1&lt;/P&gt;&lt;P&gt;Host: hott-rodd.cn&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Going against destination IP 204.69.199.39. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good luck. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Jun 2009 19:24:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/gumblar-bot-net-ips-signatures/m-p/1181425#M77059</guid>
      <dc:creator>clausonna</dc:creator>
      <dc:date>2009-06-10T19:24:49Z</dc:date>
    </item>
  </channel>
</rss>

