<?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>Securism Blog &#187; vulnerability</title>
	<atom:link href="http://blog.securism.com/tag/vulnerability/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.securism.com</link>
	<description>Simple Security.</description>
	<lastBuildDate>Tue, 31 Jan 2012 05:39:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Information Leakage via Delicious</title>
		<link>http://blog.securism.com/2009/07/information-leakage-via-delicious/</link>
		<comments>http://blog.securism.com/2009/07/information-leakage-via-delicious/#comments</comments>
		<pubDate>Fri, 10 Jul 2009 18:12:51 +0000</pubDate>
		<dc:creator>Jon Janego</dc:creator>
				<category><![CDATA[Attacks]]></category>
		<category><![CDATA[How-to]]></category>
		<category><![CDATA[attack]]></category>
		<category><![CDATA[hacking]]></category>
		<category><![CDATA[information leakage]]></category>
		<category><![CDATA[policy]]></category>
		<category><![CDATA[vulnerability]]></category>

		<guid isPermaLink="false">http://blog.securism.com/?p=207</guid>
		<description><![CDATA[<a href="http://blog.securism.com/2009/07/information-leakage-via-delicious/" title="Information Leakage via Delicious"></a>By now, the concept of &#8220;google hacking&#8221; is pretty commonly understood.  People may not be preventing it very well, but it&#8217;s moved beyond a new thing. For the uninitiated, though, here&#8217;s a brief summary: using Google (or any other search &#8230;<p class="read-more"><a href="http://blog.securism.com/2009/07/information-leakage-via-delicious/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://blog.securism.com/2009/07/information-leakage-via-delicious/" title="Information Leakage via Delicious"></a><p>By now, the concept of &#8220;google hacking&#8221; is pretty commonly understood.  People may not be preventing it very well, but it&#8217;s moved beyond a new thing.</p>
<p>For the uninitiated, though, here&#8217;s a brief summary: using Google (or any other search engine &#8211; but really, is there any other?) to find vulnerable web apps, personal information, mp3s in public directories, etc etc.  It&#8217;s great fun, and a pretty fundamental initial step of profiling an attack target.</p>
<p><a href="http://www.hackersforcharity.org/">Johnny Long</a> was one of the main evangelists of this method and has a <a href="http://johnny.ihackstuff.com/ghdb/">great database </a>of search terms.  It&#8217;s no longer actively maintained, but you can still find plenty of good information with this as a starting point!</p>
<p>So Google hacking is great, but it only gets you to the public internet.  What if I wanted to profile the inside of a company, from the outside?  And passively &#8211; without hitting their servers myself?  Wouldn&#8217;t it be great if I could look for public information shared by company insiders?</p>
<p><a href="http://delicious.com/">Delicious</a> seems almost perfectly designed to do this kind of activity.  For the unfamiliar, delicious is an online bookmarking site, designed around the idea that sharing bookmarks is a great way to learn about new sites.  Which is an alright idea&#8230;  but don&#8217;t people also bookmark a lot of private information?  I sure do!</p>
<p>Making matters worse, delicious encourages users to get started by uploading their browser bookmarks.  Essentially uploading gobs of potentially personal data to a public site.  This is a classic case of information leakage.  A dedicated attacker can use this public information to get all sorts of juicy tidbits about a company.</p>
<p>Let&#8217;s do some examples.  This all works great in theory, but, like Google, there is a LOT of data to sort through.  Say I&#8217;m a bad guy interested in insider information about a company.  I can start looking for the basics &#8211; say&#8230; &#8220;intranet&#8221;.  Delicious makes this easier by encouraging users to tag their posts for easy categorization:</p>
<p><a href="http://delicious.com/tag/intranet">http://delicious.com/tag/intranet</a></p>
<p>So that gives me everything that users have tagged with &#8216;intranet&#8217;.   Lots of sites about intranet design, usability, etc.  But also sites tagged by users to manage their own bookmarks!  So I&#8217;ll start digging into an individual company&#8230; how about AMD?</p>
<p><a href="http://delicious.com/search?p=amd&amp;u=&amp;chk=&amp;context=recent&amp;tag=intranet">http://delicious.com/search?p=amd&amp;u=&amp;chk=&amp;context=recent&amp;tag=intranet</a></p>
<p><a href="http://blog.securism.com/wordpress/wp-content/uploads/2009/07/intranet_amd.PNG"><img class="size-medium wp-image-211 alignleft" title="intranet_amd" src="http://blog.securism.com/wordpress/wp-content/uploads/2009/07/intranet_amd-300x118.PNG" alt="intranet_amd" width="300" height="118" /></a></p>
<p>The first result doesn&#8217;t look interesting, but the second and third, well those sound like intranet sites!  This is confirmed by trying to follow them through and the DNS not resolving.  Nice!  Now let&#8217;s see what else this presumed AMD employee has bookmarked&#8230;</p>
<p><a href="http://blog.securism.com/wordpress/wp-content/uploads/2009/07/links_1.PNG"><img class="alignleft size-medium wp-image-212" title="links_1" src="http://blog.securism.com/wordpress/wp-content/uploads/2009/07/links_1-300x147.PNG" alt="links_1" width="300" height="147" /></a></p>
<p>Wow, lots of development related links!  Interesting.  And what&#8217;s that link on page 2 about &#8220;AMD Manager Toolkit&#8221; ??  This fellow looks like he&#8217;s a technical manager at AMD!</p>
<p>Dig a little deeper, and it looks like we have another intranet site &#8211; mentioning the (presumably internal) code name of a project.  Interesting!  Go further into the links, and you see even further links to internal project Wiki pages.</p>
<p><a href="http://blog.securism.com/wordpress/wp-content/uploads/2009/07/links_2.PNG"><img class="alignleft size-medium wp-image-213" title="links_2" src="http://blog.securism.com/wordpress/wp-content/uploads/2009/07/links_2-300x82.PNG" alt="links_2" width="300" height="82" /></a></p>
<p>Surfing around to a few of the non-intranet sites gives me an even better profile of this person.  They work with unit testing.  They use UML, C++, and Ruby, and read a lot about circuit design.  They live in India.  They&#8217;re learning guitar, and are interested in martial arts.</p>
<p>This may seem like innocent information to an outsider, but if I was doing this for espionage purposes, I just learned a <em>lot</em> about the internal operations of a project &#8211; and this is with 10 minutes of work on one webpage.  What else could I find if I dug through the internet further?</p>
<p>Web 2.0 is a lot of fun, and can be really useful.  But what&#8217;s often overlooked are the implications of sharing all this information.  Unless you make it a point to protect your privacy, that privacy probably doesn&#8217;t exist.  And for businesses, this can be a major potential risk.</p>
<p>Delicious certainly doesn&#8217;t help stop this &#8211; according to the <a href="http://delicious.com/help/faq#socialbookmarking_privacy">FAQ</a>, you cannot make your links private by default, but instead must manually edit them to make them private.  And also, the <a href="http://delicious.com/help/terms">TOS</a> leaves responsibility entirely in the hands of the users.  Very laissez-faire!</p>
<p>Should companies ban employees from using sites like delicious?  Probably not.  But I think that this demonstrates that employees need to be more educated on what they are exposing themselves and their employer to when using social networking sites.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.securism.com/2009/07/information-leakage-via-delicious/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Gnome Do Microblogging Plugin Authenticates Over Clear Text</title>
		<link>http://blog.securism.com/2009/01/gnome-do-microblogging-plugin-authenticates-over-clear-text/</link>
		<comments>http://blog.securism.com/2009/01/gnome-do-microblogging-plugin-authenticates-over-clear-text/#comments</comments>
		<pubDate>Fri, 30 Jan 2009 21:52:04 +0000</pubDate>
		<dc:creator>Ben Hagen</dc:creator>
				<category><![CDATA[Attacks]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[ubuntu]]></category>
		<category><![CDATA[vulnerability]]></category>

		<guid isPermaLink="false">http://blog.securism.com/?p=178</guid>
		<description><![CDATA[<a href="http://blog.securism.com/2009/01/gnome-do-microblogging-plugin-authenticates-over-clear-text/" title="Gnome Do Microblogging Plugin Authenticates Over Clear Text"></a>I love the Gnome productivity tool Gnome Do. Its great! What&#8217;s not so great is the fact that the installation default Twitter plugin &#8220;Microblogging (Twitter)&#8221; version 1.0 authenticates to Twitter over clear text. In general, its a great plugin&#8230; easy &#8230;<p class="read-more"><a href="http://blog.securism.com/2009/01/gnome-do-microblogging-plugin-authenticates-over-clear-text/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://blog.securism.com/2009/01/gnome-do-microblogging-plugin-authenticates-over-clear-text/" title="Gnome Do Microblogging Plugin Authenticates Over Clear Text"></a><p>I love the Gnome productivity tool <a href="http://do.davebsd.com/">Gnome Do</a>. Its great! What&#8217;s not so great is the fact that the installation default Twitter plugin &#8220;<a href="http://do.davebsd.com/wiki/index.php?title=Microblog_Plugin">Microblogging (Twitter)</a>&#8221; version 1.0 authenticates to Twitter over clear text. In general, its a great plugin&#8230; easy to post updates and wonderful balloon popups when friends post their&#8217;s&#8230; but this is a killer problem.</p>
<p>I&#8217;ve filed a bug report with the plugins group <a href="https://bugs.launchpad.net/do-plugins/+bug/323364">here</a>.</p>
<p>With the ubiquity of wireless networks and the ease of promiscuously monitoring wireless networks, it is no longer acceptable to authenticate over clear text. Twitter shouldn&#8217;t allow authentications over none SSL channels, and applications shouldn&#8217;t support them even if non-SSL is supported. I discovered this while a friend was toying around with Kismet at a local cafe. I typically connect to an OpenSSL VPN whenever I use public networks, but due to the nature of the plugin it connects before I have a reasonable chance to enable the VPN&#8230; hence my friend captured my password. Fun.</p>
<p>I would also like to take this oppurtunity to remove any liability from myself for anything posted to my Twitter account in the future <img src='http://blog.securism.com/wordpress/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://blog.securism.com/2009/01/gnome-do-microblogging-plugin-authenticates-over-clear-text/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

