<?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 why is this event trapping? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/why-is-this-event-trapping/m-p/2793399#M44459</link>
    <description>&lt;P&gt;Using AMP8150 with 5.3.0.3&lt;/P&gt;
&lt;P&gt;I see a sig tripping that shouldn't be. 1:655:16.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Sig:&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;alert tcp $EXTERNAL_NET 113 -&amp;gt; $SMTP_SERVERS 25 (msg:"SERVER-MAIL Sendmail 8.6.9 exploit"; flow:to_server,established; content:"|0A|D/"; metadata:ruleset community, service smtp; reference:bugtraq,2311; reference:cve,1999-0204; classtype:attempted-admin; sid:655; rev:16; )&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;The device is able to detect the system is a Windows system with network/host discovery- obviously not running Sendmail. Why does this rule keep firing when Sourcefire sees Sendmail is not running?&lt;/P&gt;</description>
    <pubDate>Sun, 10 Mar 2019 13:29:35 GMT</pubDate>
    <dc:creator>greg.dzurinda</dc:creator>
    <dc:date>2019-03-10T13:29:35Z</dc:date>
    <item>
      <title>why is this event trapping?</title>
      <link>https://community.cisco.com/t5/network-security/why-is-this-event-trapping/m-p/2793399#M44459</link>
      <description>&lt;P&gt;Using AMP8150 with 5.3.0.3&lt;/P&gt;
&lt;P&gt;I see a sig tripping that shouldn't be. 1:655:16.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Sig:&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;alert tcp $EXTERNAL_NET 113 -&amp;gt; $SMTP_SERVERS 25 (msg:"SERVER-MAIL Sendmail 8.6.9 exploit"; flow:to_server,established; content:"|0A|D/"; metadata:ruleset community, service smtp; reference:bugtraq,2311; reference:cve,1999-0204; classtype:attempted-admin; sid:655; rev:16; )&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;The device is able to detect the system is a Windows system with network/host discovery- obviously not running Sendmail. Why does this rule keep firing when Sourcefire sees Sendmail is not running?&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 13:29:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/why-is-this-event-trapping/m-p/2793399#M44459</guid>
      <dc:creator>greg.dzurinda</dc:creator>
      <dc:date>2019-03-10T13:29:35Z</dc:date>
    </item>
    <item>
      <title>Because somebody is trying to</title>
      <link>https://community.cisco.com/t5/network-security/why-is-this-event-trapping/m-p/2793400#M44460</link>
      <description>&lt;P&gt;Because somebody is trying to use an sendmail exploit on your windows server.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You are not vulnerable, but they are still trying.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Nov 2016 18:04:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/why-is-this-event-trapping/m-p/2793400#M44460</guid>
      <dc:creator>Dennis Perto</dc:creator>
      <dc:date>2016-11-17T18:04:26Z</dc:date>
    </item>
  </channel>
</rss>

