<?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: Windows RPC DCOM Overflow in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/windows-rpc-dcom-overflow/m-p/1236314#M77820</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 06 Feb 2009 22:13:05 GMT</pubDate>
    <dc:creator>ncamilli</dc:creator>
    <dc:date>2009-02-06T22:13:05Z</dc:date>
    <item>
      <title>Windows RPC DCOM Overflow</title>
      <link>https://community.cisco.com/t5/network-security/windows-rpc-dcom-overflow/m-p/1236312#M77818</link>
      <description>&lt;P&gt;On a daily basis, for as long as my logs go back (over a month), my 1811 router has been flagging %IPS-4-SIGNATURE: Sig:3327 Subsig:1 Sev:5 Windows RPC DCOM Overflow and Subsig:0 multiple times daily from all different external ip addresses on random ports to one of my inside ip on port 135.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone have any idea what is going on?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advanced.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 11:29:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/windows-rpc-dcom-overflow/m-p/1236312#M77818</guid>
      <dc:creator>ncamilli</dc:creator>
      <dc:date>2019-03-10T11:29:07Z</dc:date>
    </item>
    <item>
      <title>Re: Windows RPC DCOM Overflow</title>
      <link>https://community.cisco.com/t5/network-security/windows-rpc-dcom-overflow/m-p/1236313#M77819</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It is probably the conficker/downadup worm or a variant attempting to propagate from infected systems out on the Internet.  Make sure your Windows systems are all patched and you are blocking TCP ports 135 and 445 inbound to your networks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Feb 2009 21:46:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/windows-rpc-dcom-overflow/m-p/1236313#M77819</guid>
      <dc:creator>eddie.mitchell</dc:creator>
      <dc:date>2009-02-06T21:46:32Z</dc:date>
    </item>
    <item>
      <title>Re: Windows RPC DCOM Overflow</title>
      <link>https://community.cisco.com/t5/network-security/windows-rpc-dcom-overflow/m-p/1236314#M77820</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Feb 2009 22:13:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/windows-rpc-dcom-overflow/m-p/1236314#M77820</guid>
      <dc:creator>ncamilli</dc:creator>
      <dc:date>2009-02-06T22:13:05Z</dc:date>
    </item>
    <item>
      <title>Re: Windows RPC DCOM Overflow</title>
      <link>https://community.cisco.com/t5/network-security/windows-rpc-dcom-overflow/m-p/1236315#M77821</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Well ,it's not actually advisable to publish netbios port (135-139,445) to the internet. Perhaps you should source limit it. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cheers &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Feb 2009 06:56:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/windows-rpc-dcom-overflow/m-p/1236315#M77821</guid>
      <dc:creator>yuliang13</dc:creator>
      <dc:date>2009-02-16T06:56:22Z</dc:date>
    </item>
  </channel>
</rss>

