<?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>phoenixheart - portfolio &#38; more &#187; vulnerability</title> <atom:link href="http://www.phoenixheart.net/tag/vulnerability/feed/" rel="self" type="application/rss+xml" /><link>http://www.phoenixheart.net</link> <description>phoenixheart - portfolio &#38; more</description> <lastBuildDate>Wed, 25 Aug 2010 03:02:03 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.0.1</generator> <script type="text/javascript">/*<![CDATA[*/if(typeof Meebo=="undefined"){Meebo=function(){(Meebo._=Meebo._||[]).push(arguments)};(function(q){var args=arguments;if(!document.body){return setTimeout(function(){args.callee.apply(this,args)},100);}var d=document,b=d.body,m=b.insertBefore(d.createElement('div'),b.firstChild);s=d.createElement('script');m.id='meebo';m.style.display='none';m.innerHTML='<iframe id="meebo-iframe"></iframe>';s.src='http'+(q.https?'s':'')+'://'+(q.stage?'stage-':'')+'cim.meebo.com/cim/cim.php?network='+q.network;b.insertBefore(s,b.firstChild);})({network:'phoenixheartnet_bo16we'});}/*]]>*/</script> <item><title>WP-DBManager&#8217;s vulnerability</title><link>http://www.phoenixheart.net/2009/01/wp-dbmanager-vulnerability/</link> <comments>http://www.phoenixheart.net/2009/01/wp-dbmanager-vulnerability/#comments</comments> <pubDate>Mon, 05 Jan 2009 09:12:56 +0000</pubDate> <dc:creator>phoenix.heart</dc:creator> <category><![CDATA[Blahblahblah]]></category> <category><![CDATA[Featured]]></category> <category><![CDATA[plugin]]></category> <category><![CDATA[vulnerability]]></category> <category><![CDATA[wordpress]]></category><guid
isPermaLink="false">http://www.phoenixheart.net/?p=199</guid> <description><![CDATA[I&#8217;ve been using WP-DBManager for quite a while now, and in short it&#8217;s a very good &#8211; if not the best &#8211; WordPress plugin to help you manage your database &#8211; with just one click, you can backup, restore, repair, optimize, and do other tasks. Essential plugin, really. But today I noticed this DANGEROUS thing, [...]]]></description> <content:encoded><![CDATA[<p>I&#8217;ve been using <a
href="http://lesterchan.net/portfolio/programming/php/">WP-DBManager</a> for quite a while now, and in short it&#8217;s a very good &#8211; if not the best &#8211; WordPress plugin to help you manage your database &#8211; with just one click, you can backup, restore, repair, optimize, and do other tasks. Essential plugin, really.</p><p>But today I noticed this DANGEROUS thing, and I want to announce it so that everybody can fix. By default, sql dumb data are saved into files under a directory named <strong>backup-db</strong> inside <strong>wp-content</strong>. And <em>this directory has absolutely no protection</em>. That means you can freely browse anyone&#8217;s wp-content/backup-db/ content and download the data file.</p><p>Now, I did a search of &#8220;index of /wp-content/backup-db&#8221; on Google. From the popularity of WordPress and this plugin, you can tell how many results I got. Yes, thousands of results were returned, each was a browsable and downloadable backup directory among thousands of different WordPress-powered websites.<span
id="more-199"></span></p><p>Need I stress on how serious this problem is? It&#8217;s about passwords (encrypted or not), email addresses, other private data, even credit card numbers for business blogs. This is serious.</p><h4>The fixes</h4><p>There are many fixes for this problem. You can</p><ul><li>Change the backup directory, or</li><li>Upload a index.html file into backup-db directory to prevent directory browsing, or</li><li>Use .htaccess to prohibit downloading contents from the directory etc.</li></ul><p>For the sake of WordPress users, please spread this. I&#8217;ve also contacted Lester Chan, the author of the plugin, so that he can release a fix.</p><h4>Updates</h4><p>It seems I missed the instruction from the author before installing the plugin <img
src='http://www.phoenixheart.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br
/> But anyway, I believe most of WP users just install the plugins without reading, especially when they just work out of the box. And as the downloadable sql dumps are still out there, I&#8217;m waiting for a more strict fix instead of readme file&#8217;s instruction.</p><p>UPDATE: Starting from version 2.50, the plugin author added a check for a proper .htaccess file in the backup folder for security purpose. Way to go!</p> <img
style='display:none' id="post-199-blankimage" onload="Meebo('discoverSharable', {element: ((this.parentNode.className.match('post')) ? this.parentNode : this.parentNode.parentNode) ,url:'http://www.phoenixheart.net/2009/01/wp-dbmanager-vulnerability/',title:'WP-DBManager&#8217;s vulnerability',tweet:'I&#8217;ve been using WP-DBManager for quite a while now, and in short it&#8217;s a very good &#8211',description:'I&#8217;ve been using WP-DBManager for quite a while now, and in short it&#8217;s a very good &#8211'})"><script type='text/javascript'>document.getElementById("post-199-blankimage").onload();</script>]]></content:encoded> <wfw:commentRss>http://www.phoenixheart.net/2009/01/wp-dbmanager-vulnerability/feed/</wfw:commentRss> <slash:comments>7</slash:comments> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (enhanced) (user agent is rejected)
Database Caching 4/11 queries in 0.260 seconds using disk

Served from: www.phoenixheart.net @ 2010-09-08 09:32:46 -->