<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Emposha &#187; Web Security</title>
	<atom:link href="http://www.emposha.com/category/security/feed" rel="self" type="application/rss+xml" />
	<link>http://www.emposha.com</link>
	<description>Just another stupid wordpress blog ;)</description>
	<lastBuildDate>Thu, 08 Dec 2011 13:30:45 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>PHP Shell Detector &#8211; web shell detection tool</title>
		<link>http://www.emposha.com/security/php-shell-detector-web-shell-detection-tool.html</link>
		<comments>http://www.emposha.com/security/php-shell-detector-web-shell-detection-tool.html#comments</comments>
		<pubDate>Thu, 07 Jul 2011 12:37:14 +0000</pubDate>
		<dc:creator>emposha</dc:creator>
				<category><![CDATA[Web Security]]></category>

		<guid isPermaLink="false">http://www.emposha.com/?p=442</guid>
		<description><![CDATA[PHP Shell Detector - is a php script that helps you find and identify php shells. PHP Shell Detector has a "web shells" signature database that helps to identify "web shell" up to 99%.]]></description>
			<content:encoded><![CDATA[<p>PHP Shell Detector is a php script that helps you find and identify php shells. It also has a &#8220;web shells&#8221; signature database that helps to identify &#8220;web shell&#8221; up to 99%. By using the latest javascript and css technologies, php shell detector has a light weight and friendly interface . The main features is that if you&#8217;re not sure about a suspicious file, you may send it to the <a href="http://www.websecure.co.il">websecure.co.il</a> team.  After submitting your file, it will be inspected and if there are any threats, it will be inserted into a &#8220;php shell detector&#8221; web shells signature database and the next time this file will be recognized positively.</p>
<p><strong>Screenshots</strong>:</p>
<div class="mceTemp mceIEcenter" style="text-align: center;">
<dl id="attachment_445" class="wp-caption aligncenter" style="width: 280px;">
<dt class="wp-caption-dt"><a class="portfolio-list fancy" href="http://www.emposha.com/wp-content/uploads/2011/07/shelldetect2.png"><img class="size-medium wp-image-445" title="shelldetect2" src="http://www.emposha.com/wp-content/uploads/2011/07/shelldetect2-300x189.png" alt="" width="270" height="170" /></a></dt>
<dd class="wp-caption-dd">Modal popup with suspicious functions use</dd>
</dl>
</div>
<div class="mceTemp mceIEcenter" style="text-align: center;">
<dl id="attachment_446" class="wp-caption aligncenter" style="width: 280px;">
<dt class="wp-caption-dt"><a class="portfolio-list fancy" href="http://www.emposha.com/wp-content/uploads/2011/07/shelldetect3.png"><img class="size-medium wp-image-446  fancy" title="shelldetect3" src="http://www.emposha.com/wp-content/uploads/2011/07/shelldetect3-300x201.png" alt="" width="270" height="181" /></a></dt>
<dd class="wp-caption-dd">Positive shell recognition ( suspicious functions list with ability to check what kind of function used)</dd>
</dl>
</div>
<div class="mceTemp mceIEcenter" style="text-align: center; clear: both;">
<dl id="attachment_447" class="wp-caption aligncenter" style="width: 280px;">
<dt class="wp-caption-dt"><a class="portfolio-list fancy" href="http://www.emposha.com/wp-content/uploads/2011/07/shelldetector3.5.png"><img class="size-medium wp-image-447  fancy" title="shelldetector3.5" src="http://www.emposha.com/wp-content/uploads/2011/07/shelldetector3.5-300x71.png" alt="" width="270" height="64" /></a></dt>
<dd class="wp-caption-dd">in case that shell not recognized you can always send it to websecure.co.il and they will inspect the file</dd>
</dl>
</div>
<div class="mceTemp mceIEcenter" style="text-align: center;">
<dl id="attachment_448" class="wp-caption aligncenter" style="width: 280px;">
<dt class="wp-caption-dt"><a class="portfolio-list fancy" href="http://www.emposha.com/wp-content/uploads/2011/07/shelldetector4.png"><img class="size-medium wp-image-448 " title="shelldetector4" src="http://www.emposha.com/wp-content/uploads/2011/07/shelldetector4-300x207.png" alt="" width="270" height="186" /></a></dt>
<dd class="wp-caption-dd">Report with total suspicious and shells files that was found</dd>
</dl>
</div>
<p><strong>Settings:</strong></p>
<ul>
<li>extension &#8211; extensions that should be scanned</li>
<li>showlinenumbers &#8211; show line number where suspicious function used</li>
<li>dateformat &#8211; used with access time &amp; modified time</li>
<li>langauge &#8211; if I want to use other language</li>
<li>directory &#8211; scan specific directory</li>
<li>task &#8211; perform different task</li>
<li>report_format &#8211; used with is_cron(true) file format for report file</li>
<li>is_cron &#8211; if true run like a cron(no output)</li>
<li>filelimit &#8211; maximum files to scan (more then 30000 you should scan specific directory)</li>
<li>useget &#8211; activate _GET variable for easy way to recive tasks</li>
<li>authentication &#8211; protect script with user &amp; password in case to disable simply set to NULL</li>
<li>remotefingerprint &#8211; get shells signatures db by remote</li>
</ul>
<p>&nbsp;</p>
<p><strong>Number of shells in signature database is:</strong> 141</p>
<p><strong>Demo: </strong><a href="http://www.emposha.com/demo/shelldetect/shelldetect.php">http://www.emposha.com/demo/shelldetect/</a></p>
<p><strong>Download:</strong> <a href="https://github.com/emposha/PHP-Shell-Detector">https://github.com/emposha/PHP-Shell-Detector</a></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.emposha.com/security/php-shell-detector-web-shell-detection-tool.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A New Type of Phishing Attack</title>
		<link>http://www.emposha.com/security/a-new-type-of-phishing-attack.html</link>
		<comments>http://www.emposha.com/security/a-new-type-of-phishing-attack.html#comments</comments>
		<pubDate>Tue, 25 May 2010 06:38:33 +0000</pubDate>
		<dc:creator>emposha</dc:creator>
				<category><![CDATA[Web Security]]></category>
		<category><![CDATA[Phishing Attack]]></category>

		<guid isPermaLink="false">http://www.emposha.com/?p=396</guid>
		<description><![CDATA[The web is a generative and wild place. Sometimes I think I missed my calling; being devious is so much fun. Too bad my parents brought me up with scruples.]]></description>
			<content:encoded><![CDATA[<p>The web is a generative and wild place. Sometimes I think I missed my calling; being devious is so much fun. Too bad my parents brought me up with scruples.</p>
<p>Most phishing attacks depend on an original deception. If you detect that you are at the wrong URL, or that something is amiss on a page, the chase is up. You’ve escaped the attackers. In fact, the time that wary people are most wary is exactly when they first navigate to a site.  <a href="http://www.azarask.in/blog/post/a-new-type-of-phishing-attack/">more&gt;&gt;</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.emposha.com/security/a-new-type-of-phishing-attack.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IPhone SMS Attack Unleashed</title>
		<link>http://www.emposha.com/security/iphone-sms-attack-unleashed.html</link>
		<comments>http://www.emposha.com/security/iphone-sms-attack-unleashed.html#comments</comments>
		<pubDate>Thu, 30 Jul 2009 23:20:01 +0000</pubDate>
		<dc:creator>emposha</dc:creator>
				<category><![CDATA[Web Security]]></category>
		<category><![CDATA[apple]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[sms]]></category>

		<guid isPermaLink="false">http://www.emposha.com/?p=316</guid>
		<description><![CDATA[The bug was discovered by noted iPhone hacker Charlie Miller, who first talked about the issue at the SyScan conference in Singapore. At the time, he said he'd discovered a way to crash the iPhone via SMS, and that he thought that the crash could ultimately lead to working attack code.]]></description>
			<content:encoded><![CDATA[<p>The bug was discovered by noted iPhone hacker Charlie Miller, who first talked about the issue at the <a href="http://www.syscan.org/Sg/singaporeconference.html" target="_blank">SyScan</a> conference in Singapore. At the time, he said he&#8217;d discovered a way to crash the iPhone via SMS, and that he thought that the crash could ultimately lead to working attack code.</p>
<p>But still the experts say that &#8220;<a title="iPhone Latest Hack Not So Scary" rel="bookmark" href="http://community.zdnet.co.uk/blog/0,1000000567,10013351o-2000440756b,00.htm">iPhone Security: Latest Hack Not So Scary</a>. So time will show <img src='http://www.emposha.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://www.emposha.com/security/iphone-sms-attack-unleashed.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mozilla Firefox 3.5 Memory Corruption Vulnerability</title>
		<link>http://www.emposha.com/security/mozilla-firefox-3-5-memory-corruption-vulnerability.html</link>
		<comments>http://www.emposha.com/security/mozilla-firefox-3-5-memory-corruption-vulnerability.html#comments</comments>
		<pubDate>Tue, 14 Jul 2009 19:35:41 +0000</pubDate>
		<dc:creator>emposha</dc:creator>
				<category><![CDATA[Web Security]]></category>

		<guid isPermaLink="false">http://www.emposha.com/?p=306</guid>
		<description><![CDATA[The vulnerability is caused due to an error when processing JavaScript code handling e.g. "font" HTML tags and can be exploited to cause a memory corruption. Successful exploitation allows execution of arbitrary code.]]></description>
			<content:encoded><![CDATA[<p>SBerry has discovered a vulnerability in Mozilla Firefox, which can be exploited by malicious people to compromise a user&#8217;s system.</p>
<p>The vulnerability is caused due to an error when processing JavaScript code handling e.g. &#8220;font&#8221; HTML tags and can be exploited to cause a memory corruption.</p>
<p>Successful exploitation allows execution of arbitrary code.</p>
<p>The vulnerability is confirmed in version 3.5. Other versions may also be affected.</p>
<p>Source: <a href="http://secunia.com/advisories/35798/">http://secunia.com/advisories/35798/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.emposha.com/security/mozilla-firefox-3-5-memory-corruption-vulnerability.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Beware of two critical vulnerabilities in Firefox 3</title>
		<link>http://www.emposha.com/security/beware-of-two-critical-vulnerabilities-in-firefox-3.html</link>
		<comments>http://www.emposha.com/security/beware-of-two-critical-vulnerabilities-in-firefox-3.html#comments</comments>
		<pubDate>Sat, 28 Mar 2009 21:20:41 +0000</pubDate>
		<dc:creator>emposha</dc:creator>
				<category><![CDATA[Web Security]]></category>
		<category><![CDATA[firefox]]></category>
		<category><![CDATA[vulnerability]]></category>

		<guid isPermaLink="false">http://www.emposha.com/?p=198</guid>
		<description><![CDATA[Mozilla's security team is rushing out a fix for its flagship Mozilla browser following the public release of attack code that targets a previously unknown vulnerability.]]></description>
			<content:encoded><![CDATA[<p>The exploit was released Wednesday online. It attacks a vulnerability present on Windows, Mac and Linux versions of the browser and could be used to surreptitiously execute malware on the machines of users who browse booby-trapped websites.</p>
<p><a href="http://www.theregister.co.uk/2009/03/26/new_firefox_exploit/" target="_blank">More</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.emposha.com/security/beware-of-two-critical-vulnerabilities-in-firefox-3.html/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

