<?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: 3340-0, Windows Shell External Handler in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/3340-0-windows-shell-external-handler/m-p/506726#M89709</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Regarding #2, That's most likely what it is. This is a stream based signature, so the regex doesn't have to fall inside one particular packet, it has to be in the stream of reassembled packets. Turning on the signature action "Produce Verbose Alert" will give you more context, and you may be able to catch the end colon.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding #1, Really there's no difference between ":" or "[:]" (minus the quotes) in a regex. The brackets denote a character class so [abc] means one of either a or b or c. In the case of [:] it's a character class with only one character. There is a reason that you see one value character classes in our signatures, and it simply comes down to readability... it's easy to miss something like a single colon wedged in amongst a large regex, it's not so easy to miss it when we stick it into a character class.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 09 Jun 2006 14:03:07 GMT</pubDate>
    <dc:creator>wsulym</dc:creator>
    <dc:date>2006-06-09T14:03:07Z</dc:date>
    <item>
      <title>3340-0, Windows Shell External Handler</title>
      <link>https://community.cisco.com/t5/network-security/3340-0-windows-shell-external-handler/m-p/506725#M89708</link>
      <description>&lt;P&gt;We saw a couple of these yesterday. What concerns me is that the trigger packet does not contain a string that matches the regex. I have 2 questions:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) What is the point of putting brackets around the colon at the end of the regex? This is done in other regex's as well (single character enclosed in square brackets), so there must be a point right?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) Where is the colon in the trigger packet?&lt;/P&gt;&lt;P&gt;UPDATE: duh. I figured this out...it must be in the next packet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is the regex:&lt;/P&gt;&lt;P&gt;[=].?[Ss][Hh][Ee][Ll][Ll][:]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is the alarm:&lt;/P&gt;&lt;P&gt;evIdsAlert: eventId=1136129594516778202  vendor=Cisco  severity=high  &lt;/P&gt;&lt;P&gt;  originator:   &lt;/P&gt;&lt;P&gt;    hostId: 27-fw-dmz-c1  &lt;/P&gt;&lt;P&gt;    appName: sensorApp  &lt;/P&gt;&lt;P&gt;    appInstanceId: 14978  &lt;/P&gt;&lt;P&gt;  time: June 9, 2006 12:46:51 AM UTC  offset=-300  timeZone=GMT-06:00  &lt;/P&gt;&lt;P&gt;  signature:   description=Windows Shell External Handler  id=3340  version=S102  &lt;/P&gt;&lt;P&gt;    subsigId: 0  &lt;/P&gt;&lt;P&gt;    sigDetails: =shell:  &lt;/P&gt;&lt;P&gt;  interfaceGroup:   &lt;/P&gt;&lt;P&gt;  vlan: 0  &lt;/P&gt;&lt;P&gt;  participants:   &lt;/P&gt;&lt;P&gt;    attacker:   &lt;/P&gt;&lt;P&gt;      addr: 4.78.168.81  locality=ANY  &lt;/P&gt;&lt;P&gt;      port: 80  &lt;/P&gt;&lt;P&gt;    target:   &lt;/P&gt;&lt;P&gt;      addr: 206.195.195.101  locality=NETCACHE_EXT_IP  &lt;/P&gt;&lt;P&gt;      port: 5049  &lt;/P&gt;&lt;P&gt;  context:   &lt;/P&gt;&lt;P&gt;    fromAttacker: &lt;/P&gt;&lt;P&gt;000000  66 66 6F 6E 20 75 6E 64  65 72 20 6C 61 79 65 72  ffon under layer&lt;/P&gt;&lt;P&gt;000010  22 3B 73 35 5B 31 5D 3D  73 37 3B 76 61 72 20 73  ";s5[1]=s7;var s&lt;/P&gt;&lt;P&gt;000020  38 3D 22 41 6C 6C 6F 76  65 72 20 64 65 6C 69 63  8="Allover delic&lt;/P&gt;&lt;P&gt;000030  61 74 65 20 62 65 61 64  65 64 20 61 70 70 6C 69  ate beaded appli&lt;/P&gt;&lt;P&gt;000040  71 75 5C 75 30 30 45 39  22 3B 73 35 5B 32 5D 3D  qu\u00E9";s5[2]=&lt;/P&gt;&lt;P&gt;000050  73 38 3B 76 61 72 20 73  39 3D 22 48 61 6C 74 65  s8;var s9="Halte&lt;/P&gt;&lt;P&gt;000060  72 20 74 69 65 73 20 69  6E 20 62 61 63 6B 20 6F  r ties in back o&lt;/P&gt;&lt;P&gt;000070  66 20 6E 65 63 6B 3B 20  76 2D 6E 65 63 6B 22 3B  f neck; v-neck";&lt;/P&gt;&lt;P&gt;000080  73 35 5B 33 5D 3D 73 39  3B 76 61 72 20 73 31 30  s5[3]=s9;var s10&lt;/P&gt;&lt;P&gt;000090  3D 22 53 61 73 68 20 74  69 65 73 20 69 6E 20 62  ="Sash ties in b&lt;/P&gt;&lt;P&gt;0000A0  61 63 6B 3B 20 66 6C 61  72 65 64 20 68 65 6D 22  ack; flared hem"&lt;/P&gt;&lt;P&gt;0000B0  3B 73 35 5B 34 5D 3D 73  31 30 3B 76 61 72 20 73  ;s5[4]=s10;var s&lt;/P&gt;&lt;P&gt;0000C0  31 31 3D 22 53 6E 61 70  2D 63 6C 6F 73 75 72 65  11="Snap-closure&lt;/P&gt;&lt;P&gt;0000D0  20 61 74 20 62 61 63 6B  3B 20 66 61 6C 6C 73 20   at back; falls &lt;/P&gt;&lt;P&gt;0000E0  74 6F 20 68 69 70 22 3B  73 35 5B 35 5D 3D 73 31  to hip";s5[5]=s1&lt;/P&gt;&lt;P&gt;0000F0  31 3B 76 61 72 20 73 31  32 3D 22 53 68 65 6C 6C  1;var s12="Shell&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  riskRatingValue: 60  &lt;/P&gt;&lt;P&gt;  interface: ge0_0  &lt;/P&gt;&lt;P&gt;  protocol: tcp  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 10:03:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/3340-0-windows-shell-external-handler/m-p/506725#M89708</guid>
      <dc:creator>mhellman</dc:creator>
      <dc:date>2019-03-10T10:03:11Z</dc:date>
    </item>
    <item>
      <title>Re: 3340-0, Windows Shell External Handler</title>
      <link>https://community.cisco.com/t5/network-security/3340-0-windows-shell-external-handler/m-p/506726#M89709</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Regarding #2, That's most likely what it is. This is a stream based signature, so the regex doesn't have to fall inside one particular packet, it has to be in the stream of reassembled packets. Turning on the signature action "Produce Verbose Alert" will give you more context, and you may be able to catch the end colon.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding #1, Really there's no difference between ":" or "[:]" (minus the quotes) in a regex. The brackets denote a character class so [abc] means one of either a or b or c. In the case of [:] it's a character class with only one character. There is a reason that you see one value character classes in our signatures, and it simply comes down to readability... it's easy to miss something like a single colon wedged in amongst a large regex, it's not so easy to miss it when we stick it into a character class.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Jun 2006 14:03:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/3340-0-windows-shell-external-handler/m-p/506726#M89709</guid>
      <dc:creator>wsulym</dc:creator>
      <dc:date>2006-06-09T14:03:07Z</dc:date>
    </item>
  </channel>
</rss>

