{"id":10,"date":"2014-11-06T21:08:08","date_gmt":"2014-11-06T20:08:08","guid":{"rendered":"http:\/\/www.herbiez.com\/?p=10"},"modified":"2024-01-16T22:27:02","modified_gmt":"2024-01-17T04:27:02","slug":"security-onion-and-elsa-issues","status":"publish","type":"post","link":"https:\/\/www.herbiez.com\/?p=10","title":{"rendered":"Security Onion and Elsa issues"},"content":{"rendered":"<p>So the other day while reviewing alerts in Squert I noticed a lot of alerts triggering for &#8216;ET POLICY SSLv3 outbound connection from client vulnerable to POODLE attack.&#8217; The rule for this is:<\/p>\n<blockquote><p>alert tcp $EXTERNAL_NET [443,465,993,995,25] -&amp;gt; $HOME_NET any (msg:&#8221;ET POLICY SSLv3 outbound connection from client vulnerable to POODLE attack&#8221;; flow:established,from_server; ssl_version:sslv3; ssl_state:server_hello; content:&#8221;|16 03 00|&#8221;; depth:3; threshold: type limit, track by_src, seconds 300, count 1; reference:cve,2014-3566; reference:url,blog.fox-it.com\/2014\/10\/15\/poodle\/; reference:url,www.openssl.org\/~bodo\/ssl-poodle.pdf; reference:url,askubuntu.com\/questions\/537196\/how-do-i-patch-workaround-sslv3-poodle-vulnerability-cve-2014-3566; reference:url,www.imperialviolet.org\/2014\/10\/14\/poodle.html; classtype:policy-violation; sid:2019416; rev:3;)<\/p><\/blockquote>\n<p>This got me thinking why am I just now starting to see this alert after running SO for a couple months now? Looking into the events I started noticing how they were all stemming from our kid&#8217;s Android tablets. And of course since the alerts were over port 443 I could not see anything in the PCAPs. So I figured the next best thing would be to start looking through Elsa to see if I could find out when this started and if there was any pattern to these events. I proceeded to find out that Elsa had stopped archiving events a LONG time ago (about a month and a half ago). The first place I started to troubleshoot thingswas with the command &#8216;SOSTAT.&#8217; That showed me a high amount of files sitting in the Elsa buffers section of the report (about 280+).<\/p>\n<p><!--more--><\/p>\n<p>Googling around trying to find out why Elsa stopped working (actually archiving events) I stumbled across <a href=\"http:\/\/groups.google.com\/forum\/#!searchin\/security-onion\/elsa$20dates\/security-onion\/_AdAsOvZP7Q\/TlCZvOIZsUUJ\">this thread<\/a>. I started to go through the node.log file looking for errors and found errors such as these<\/p>\n<blockquote><p>ERROR [2014\/11\/01 17:08:04] \/opt\/elsa\/web\/..\/node\/\/Indexer.pm (1142) Indexer::_queue_for_indexing 31700 [undef]<br \/>\n* ERROR [2014\/11\/01 17:09:03] \/opt\/elsa\/web\/..\/node\/\/Indexer.pm (948) Indexer::load_buffers 31735 [undef]<br \/>\n* ERROR [2014\/11\/01 17:09:03] \/opt\/elsa\/web\/..\/node\/\/Indexer.pm (1142) Indexer::_queue_for_indexing 31735 [undef]<br \/>\n* ERROR [2014\/11\/01 17:10:03] \/opt\/elsa\/web\/..\/node\/\/Indexer.pm (948) Indexer::load_buffers 31776 [undef]<br \/>\n* ERROR [2014\/11\/01 17:10:04] \/opt\/elsa\/web\/..\/node\/\/Indexer.pm (1142) Indexer::_queue_for_indexing 31776 [undef]<br \/>\n* ERROR [2014\/11\/01 17:11:03] \/opt\/elsa\/web\/..\/node\/\/Indexer.pm (948) Indexer::load_buffers 32062 [undef]<br \/>\n* ERROR [2014\/11\/01 17:11:03] \/opt\/elsa\/web\/..\/node\/\/Indexer.pm (1142) Indexer::_queue_for_indexing 32062 [undef]<br \/>\n* ERROR [2014\/11\/01 17:12:03] \/opt\/elsa\/web\/..\/node\/\/Indexer.pm (948) Indexer::load_buffers 32087 [undef]<br \/>\n* ERROR [2014\/11\/01 17:12:03] \/opt\/elsa\/web\/..\/node\/\/Indexer.pm (1142) Indexer::_queue_for_indexing 32087 [undef]<br \/>\n* ERROR [2014\/11\/01 17:13:02] \/opt\/elsa\/web\/..\/node\/\/Indexer.pm (948) Indexer::load_buffers 32123 [undef]<br \/>\n* ERROR [2014\/11\/01 17:13:03] \/opt\/elsa\/web\/..\/node\/\/Indexer.pm (1142) Indexer::_queue_for_indexing 32123 [undef]<br \/>\n* ERROR [2014\/11\/01 17:14:02] \/opt\/elsa\/web\/..\/node\/\/Indexer.pm (948) Indexer::load_buffers 32146 [undef]<br \/>\n* ERROR [2014\/11\/01 17:14:02] \/opt\/elsa\/web\/..\/node\/\/Indexer.pm (1142) Indexer::_queue_for_indexing 32146 [undef]<\/p><\/blockquote>\n<p>Now since I am running SecurityOnion as a VM on a laptop with a bad battery, there had been some &#8220;unexpected&#8221; shutdowns. So just on the off chance that I borked the database, I ran the command &#8216;sudo mysqlcheck -A&#8217;. Nothing came back corrupted. YIPPEE! I tried to restart just the syslog_ng service to see if that would kick start things&#8230; Nope no go there either.<\/p>\n<p>So going back to the node.log file for Elsa, I noticed the following line:<\/p>\n<blockquote><p>Total mem used: 770549356 of 3082194944, which is greater than 25 allowed percent<\/p><\/blockquote>\n<p>in the log file. Based on the post from above, I tried restarting the syslog_ng service and watching what was being written to the log file. This time I saw it in real-time. It was here that it dawned on me that this was relating back to a line that I saw in the \/etc\/elsa_node.conf file:<\/p>\n<blockquote><p># Check to be sure that temporary indexes (which use a lot of RAM) never go above this amount of RAM, or they will be prematurely consolidated.<br \/>\n&#8220;allowed_mem_percent&#8221;: 25,<\/p><\/blockquote>\n<p>I made a quick change to the file; changing the &#8217;25&#8217; to &#8217;35&#8217; and then restarted the syslog_ng service. Once I did that, the files in the buffer started to go down again and Elsa started processing things again.<\/p>\n<p>Now back to trying to figure out why I am seeing the POODLE alert.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>So the other day while reviewing alerts in Squert I noticed a lot of alerts triggering for &#8216;ET POLICY SSLv3 outbound connection from client vulnerable to POODLE attack.&#8217; The rule for this is: alert tcp $EXTERNAL_NET [443,465,993,995,25] -&amp;gt; $HOME_NET any (msg:&#8221;ET POLICY SSLv3 outbound connection from client vulnerable to POODLE attack&#8221;; flow:established,from_server; ssl_version:sslv3; ssl_state:server_hello; content:&#8221;|16 03 00|&#8221;; depth:3; threshold: type limit, track by_src, seconds 300, count 1; reference:cve,2014-3566; reference:url,blog.fox-it.com\/2014\/10\/15\/poodle\/; reference:url,www.openssl.org\/~bodo\/ssl-poodle.pdf; reference:url,askubuntu.com\/questions\/537196\/how-do-i-patch-workaround-sslv3-poodle-vulnerability-cve-2014-3566; reference:url,www.imperialviolet.org\/2014\/10\/14\/poodle.html; classtype:policy-violation; sid:2019416; rev:3;) This got me thinking why am I just now starting to see this alert after running SO for a couple months now? Looking into the&#8230;<\/p>\n<p> <a class=\"continue-reading-link\" href=\"https:\/\/www.herbiez.com\/?p=10\"><span>Continue reading<\/span><i class=\"crycon-right-dir\"><\/i><\/a> <\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[3,2],"class_list":["post-10","post","type-post","status-publish","format-standard","hentry","category-security-onion","tag-nsm","tag-securityonion"],"_links":{"self":[{"href":"https:\/\/www.herbiez.com\/index.php?rest_route=\/wp\/v2\/posts\/10","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.herbiez.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.herbiez.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.herbiez.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.herbiez.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=10"}],"version-history":[{"count":16,"href":"https:\/\/www.herbiez.com\/index.php?rest_route=\/wp\/v2\/posts\/10\/revisions"}],"predecessor-version":[{"id":1650,"href":"https:\/\/www.herbiez.com\/index.php?rest_route=\/wp\/v2\/posts\/10\/revisions\/1650"}],"wp:attachment":[{"href":"https:\/\/www.herbiez.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=10"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.herbiez.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=10"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.herbiez.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=10"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}