<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: WordPress </title>
	<atom:link href="http://blogsecurity.net/wordpress/wordpress-2-8-3-reset-admin-password-vulnerability/feed" rel="self" type="application/rss+xml" />
	<link>http://blogsecurity.net/wordpress/wordpress-2-8-3-reset-admin-password-vulnerability</link>
	<description>Always something worth reading...</description>
	<lastBuildDate>Fri, 12 Mar 2010 11:09:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andy Fitzpatrick</title>
		<link>http://blogsecurity.net/wordpress/wordpress-2-8-3-reset-admin-password-vulnerability/comment-page-1#comment-16912</link>
		<dc:creator>Andy Fitzpatrick</dc:creator>
		<pubDate>Tue, 20 Oct 2009 11:24:16 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=578#comment-16912</guid>
		<description>I updated to 2.8.4 and couldn&#039;t believe how simple the upgrade procedure is. Just one keypress and it&#039;s sorted</description>
		<content:encoded><![CDATA[<p>I updated to 2.8.4 and couldn&#8217;t believe how simple the upgrade procedure is. Just one keypress and it&#8217;s sorted</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MustLive</title>
		<link>http://blogsecurity.net/wordpress/wordpress-2-8-3-reset-admin-password-vulnerability/comment-page-1#comment-16765</link>
		<dc:creator>MustLive</dc:creator>
		<pubDate>Sun, 16 Aug 2009 17:50:09 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=578#comment-16765</guid>
		<description>David, as you could hear, in WordPress 2.8.4 this hole was fixed.

Guys, about working this vulnerability in different PHP versions. As I tested just after I wrote previous comment, empty() works fine - the problem not in it. I tested work of empty() with arrays on my old PHP and it&#039;s works fine, and also I checked this vulnerability on one of the latest PHP versions and empty() worked, but hole didn&#039;t. So problem not in empty().

After I made additional research (in different WP versions), I found that attack not work at the second check - when picking out from DB to $user variable and checking it. The code in WP 2.8.3 and those older versions which I checked are similar, but hole doesn&#039;t work. Also I checked on MySQL 4.x and 5.x, and the hole still didn&#039;t work (i.e. there is no difference on various MySQL versions). So anyone can test it in different WP versions by himself to find vulnerable ones. So it&#039;s strange why this hole doesn&#039;t want to work in older versions of WP :).</description>
		<content:encoded><![CDATA[<p>David, as you could hear, in WordPress 2.8.4 this hole was fixed.</p>
<p>Guys, about working this vulnerability in different PHP versions. As I tested just after I wrote previous comment, empty() works fine &#8211; the problem not in it. I tested work of empty() with arrays on my old PHP and it&#8217;s works fine, and also I checked this vulnerability on one of the latest PHP versions and empty() worked, but hole didn&#8217;t. So problem not in empty().</p>
<p>After I made additional research (in different WP versions), I found that attack not work at the second check &#8211; when picking out from DB to $user variable and checking it. The code in WP 2.8.3 and those older versions which I checked are similar, but hole doesn&#8217;t work. Also I checked on MySQL 4.x and 5.x, and the hole still didn&#8217;t work (i.e. there is no difference on various MySQL versions). So anyone can test it in different WP versions by himself to find vulnerable ones. So it&#8217;s strange why this hole doesn&#8217;t want to work in older versions of WP :).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MustLive</title>
		<link>http://blogsecurity.net/wordpress/wordpress-2-8-3-reset-admin-password-vulnerability/comment-page-1#comment-16756</link>
		<dc:creator>MustLive</dc:creator>
		<pubDate>Fri, 14 Aug 2009 20:31:58 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=578#comment-16756</guid>
		<description>dt, nice and compact fix.

Jesper.

You are right. For example, I by myself make a lot of security checking in WordPress which I&#039;m using (in all version which I used from 2.0.3 and higher). And I found many holes in WP, some of them I disclosed, some I&#039;d do later.

But I did&#039;n saw this issue in wp-login.php, because I thought that &quot;if ( empty($key) )&quot; is enough protection, but as Laurent showed it&#039;s not (and it can be byppased by using of array). On the other hand, as I wrote before, in my version of PHP this code works fine and doesn&#039;t allow to bypass this check. It&#039;s possible that in older versions of PHP empty() works fine in such cases.</description>
		<content:encoded><![CDATA[<p>dt, nice and compact fix.</p>
<p>Jesper.</p>
<p>You are right. For example, I by myself make a lot of security checking in WordPress which I&#8217;m using (in all version which I used from 2.0.3 and higher). And I found many holes in WP, some of them I disclosed, some I&#8217;d do later.</p>
<p>But I did&#8217;n saw this issue in wp-login.php, because I thought that &#8220;if ( empty($key) )&#8221; is enough protection, but as Laurent showed it&#8217;s not (and it can be byppased by using of array). On the other hand, as I wrote before, in my version of PHP this code works fine and doesn&#8217;t allow to bypass this check. It&#8217;s possible that in older versions of PHP empty() works fine in such cases.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MustLive</title>
		<link>http://blogsecurity.net/wordpress/wordpress-2-8-3-reset-admin-password-vulnerability/comment-page-1#comment-16755</link>
		<dc:creator>MustLive</dc:creator>
		<pubDate>Fri, 14 Aug 2009 20:20:20 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=578#comment-16755</guid>
		<description>&gt; You shouldn’t really be using 2.0.x branch any more as its no longer maintained.
David, I&#039;ve planed already to write a comment in your post about 2.0.x branch and I&#039;d do it soon ;-).

Don&#039;t worry I have never expected on WP guys and always tried to fix all holes by myself. I always exepect only on myself.

&gt; Perhaps you could diff 2.6.2 and 2.8.3 wp-login files to see whats different.
I looked &quot;on eye&quot; sources of wp-login.php in 2.0.11, 2.6.2 and snippets from exploit and the idea of these files&#039; work is the same. In 2.6.2 and 2.8.3 these parts of code looks equal. The &quot;if ( empty($key) )&quot; line is the same in all these versions.

I have an assumption that it&#039;s because of my PHP version and those PHP versions which you and Laurent Gaffié were tested. Maybe empty() in different PHP versions works differenly with arrays.</description>
		<content:encoded><![CDATA[<p>&gt; You shouldn’t really be using 2.0.x branch any more as its no longer maintained.<br />
David, I&#8217;ve planed already to write a comment in your post about 2.0.x branch and I&#8217;d do it soon ;-).</p>
<p>Don&#8217;t worry I have never expected on WP guys and always tried to fix all holes by myself. I always exepect only on myself.</p>
<p>&gt; Perhaps you could diff 2.6.2 and 2.8.3 wp-login files to see whats different.<br />
I looked &#8220;on eye&#8221; sources of wp-login.php in 2.0.11, 2.6.2 and snippets from exploit and the idea of these files&#8217; work is the same. In 2.6.2 and 2.8.3 these parts of code looks equal. The &#8220;if ( empty($key) )&#8221; line is the same in all these versions.</p>
<p>I have an assumption that it&#8217;s because of my PHP version and those PHP versions which you and Laurent Gaffié were tested. Maybe empty() in different PHP versions works differenly with arrays.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Blamey (steveblamey) 's status on Thursday, 13-Aug-09 08:20:27 UTC - Identi.ca</title>
		<link>http://blogsecurity.net/wordpress/wordpress-2-8-3-reset-admin-password-vulnerability/comment-page-1#comment-16749</link>
		<dc:creator>Steve Blamey (steveblamey) 's status on Thursday, 13-Aug-09 08:20:27 UTC - Identi.ca</dc:creator>
		<pubDate>Thu, 13 Aug 2009 08:20:39 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=578#comment-16749</guid>
		<description>[...]  http://blogsecurity.net/wordpress/wordpress-2-8-3-reset-admin-password-vulnerability  [...]</description>
		<content:encoded><![CDATA[<p>[...]  <a href="http://blogsecurity.net/wordpress/wordpress-2-8-3-reset-admin-password-vulnerability" rel="nofollow">http://blogsecurity.net/wordpress/wordpress-2-8-3-reset-admin-password-vulnerability</a>  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesper Wallin</title>
		<link>http://blogsecurity.net/wordpress/wordpress-2-8-3-reset-admin-password-vulnerability/comment-page-1#comment-16746</link>
		<dc:creator>Jesper Wallin</dc:creator>
		<pubDate>Wed, 12 Aug 2009 18:02:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=578#comment-16746</guid>
		<description>I&#039;d say, if security is a priority, make sure you either know how the software you&#039;re running works, or don&#039;t use it at all. :)


Regards,
Zelest</description>
		<content:encoded><![CDATA[<p>I&#8217;d say, if security is a priority, make sure you either know how the software you&#8217;re running works, or don&#8217;t use it at all. :)</p>
<p>Regards,<br />
Zelest</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wordpress 2.8.4緊急升級 &#171; 活在當下</title>
		<link>http://blogsecurity.net/wordpress/wordpress-2-8-3-reset-admin-password-vulnerability/comment-page-1#comment-16742</link>
		<dc:creator>Wordpress 2.8.4緊急升級 &#171; 活在當下</dc:creator>
		<pubDate>Wed, 12 Aug 2009 15:40:51 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=578#comment-16742</guid>
		<description>[...] WordPress &lt;= 2.8.3 Reset Admin Password Vulnerability [...]</description>
		<content:encoded><![CDATA[<p>[...] WordPress &lt;= 2.8.3 Reset Admin Password Vulnerability [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simple Plugin To Protect Wordpress Against Password Reset Vulnerability</title>
		<link>http://blogsecurity.net/wordpress/wordpress-2-8-3-reset-admin-password-vulnerability/comment-page-1#comment-16741</link>
		<dc:creator>Simple Plugin To Protect Wordpress Against Password Reset Vulnerability</dc:creator>
		<pubDate>Wed, 12 Aug 2009 11:30:41 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=578#comment-16741</guid>
		<description>[...] Since morning I have been reading about latest password reset vulnerability found in wordpress  version &lt;= 2.8.3. (Details) [...]</description>
		<content:encoded><![CDATA[<p>[...] Since morning I have been reading about latest password reset vulnerability found in wordpress  version &lt;= 2.8.3. (Details) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WordPres 2.8.4 erschienen &#124; svenkubiak.de</title>
		<link>http://blogsecurity.net/wordpress/wordpress-2-8-3-reset-admin-password-vulnerability/comment-page-1#comment-16737</link>
		<dc:creator>WordPres 2.8.4 erschienen &#124; svenkubiak.de</dc:creator>
		<pubDate>Wed, 12 Aug 2009 07:07:42 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=578#comment-16737</guid>
		<description>[...] Bei der Version 2.8.4 handelt es sich ebenfalls um ein Sicherheitsupdate (für das es bereits einen Exploit gibt), so dass auch hier ein zeitnahes Update obligatorisch [...]</description>
		<content:encoded><![CDATA[<p>[...] Bei der Version 2.8.4 handelt es sich ebenfalls um ein Sicherheitsupdate (für das es bereits einen Exploit gibt), so dass auch hier ein zeitnahes Update obligatorisch [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DK</title>
		<link>http://blogsecurity.net/wordpress/wordpress-2-8-3-reset-admin-password-vulnerability/comment-page-1#comment-16736</link>
		<dc:creator>DK</dc:creator>
		<pubDate>Wed, 12 Aug 2009 05:37:03 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=578#comment-16736</guid>
		<description>MustLive, thanks for the additional tests. I tested it on WP 2.8.3.

You shouldn&#039;t really be using 2.0.x branch any more as its no longer maintained. Perhaps you could diff 2.6.2 and 2.8.3 wp-login files to see whats different.</description>
		<content:encoded><![CDATA[<p>MustLive, thanks for the additional tests. I tested it on WP 2.8.3.</p>
<p>You shouldn&#8217;t really be using 2.0.x branch any more as its no longer maintained. Perhaps you could diff 2.6.2 and 2.8.3 wp-login files to see whats different.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
