Alexander Concha sent us an email today discussing a vulnerability he has just released for WordPress 2.2.
The vulnerability is another SQL Injection vulnerability in xmlrpc.php affecting WordPress 2.2 (and most likely all versions).
The risk of the attack is slightly less-severe as it requires authentication. According to Alex one requires atleast a subscriber level account to exploit the hole. He has also released a proof of concept exploit that dumps a list of usernames and hashed passwords from the database.
WordPress have released a fix for the vulnerability, and it is fairly trivial to patch:
- Go to your WordPress root directory
- Make a copy of your xmlrpc.php file. Edit the original xmlrpc.php and find the following code:
$max_results = $args[4];
- Add (int) before $args like this:
$max_results = (int) $args[4];
- Save and exit
Alex, thanks for letting us know and keep up the great work. An english version of his post is available here.
WordPress BlogWatch has been updated to reflect this finding.
You mean like this?
$max_results = (int) $args[4];
Rod, quite correct, thanks for that. If in doubt please see: http://trac.wordpress.org/changeset/5570
[...] has a post about another SQL injection vulnerability, this time in WordPress 2.2, although it turns out to not [...]
[...] ist im gerade mal 2 Wochen alten Wordpress eine neue Sicherheitslücke aufgetaucht. Vermutlich sind auch die Vorgängerversionen [...]
WordPress 2.2 Vulnerability…
有用 WordPress 的人都要記得補洞啊~
剛看到一篇文章,提到說有人找到了 WordPress XMLRPC 的洞,包括 2.2 以前的全系列應該都會有影響 (不過,至少要先有一個 subscriber level 以上的帳號,所以先不…
[...] 中文化 « Cheat Sheet 速查表大集合 五月31st WordPress 2.2 再爆新弱點 2 Views · No Comments funp_genButton(”);WordPress 2.13 版時有人發現滿嚴重的 admin-ajax.php 漏洞,但是到了 2.2 版還是又被人抓到洞了= =” 如果您的 WP 擁有一個 Subscriber 等級以上的帳號就會有危害,請立即 patch [...]
Sicherheitslücke in Wordpress 2.2…
Eine Sicherheitslücke, die sich wahrscheinlich nicht nur in der aktuellen Wordpress-Version wiederfindet, ermöglicht einen Angriff via SQL-Injection, durch den sich offensichtlich auch die Userdaten auslesen lassen.
Betroffen ist die Datei xml…
[...] 今天在這篇文章中提到有人發現wordpress 2.2版的安全性漏洞 如果有一個subscriber等級以上的帳號就可能會有危險 但是修補方法其實很簡單 打開根目錄底下的xmlrpc.php 找到這一行程式碼 $max_results = $args[4]; [...]
[...] ad Agerry per la segnalazione. Post su Blogsecurity. [...]
[...] Auf Blog Ssecurity findet man die Infos auch auf [...]