full-disclosure - Re: DoS via tables corruption in WordPress

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Mon, 10 Feb 2014 15:05:05 +0000
From: Harry Metcalfe <harry@....com>
To: full-disclosure@...ts.grok.org.uk
Subject: Re: DoS via tables corruption in WordPress

I have a similar frustration. We operate a lot of WordPress sites and 
our clients value us, in part, because of our good security posture.

As such your emails always catch my attention and I always read them 
promptly. But I often find a lack of detail that allows me to understand 
whether they're issues that need me to take action, or just stuff it's 
interesting to be aware of.

It would be useful if you could include steps to replicate the issues 
you find.

Harry


On 10/02/2014 13:35, Aris Adamantiadis wrote:
> Hi,
>
> In none of your papers you document (in english) how you manage to
> produce a table corruption in mysql, let alone from the web layers. I
> still think that's possible because I experienced it on my own wordpress
> + mysql (had to do a manual repair), be it from an accident or your own
> exploit.
>
> Don't you think that's a bug in mysql itself ? Being able to corrupt
> tables using basic SQL statements like insert and select should not be
> possible.
>
> Thanks,
>
> Aris
>
> Le 10/02/14 14:02, MustLive a écrit :
>> Hello participants of Mailing List.
>>
>> There is DoS vulnerability in WordPress, about which I wrote in 2009
>> (http://websecurity.com.ua/3152/, on English
>> http://perishablepress.com/important-security-fix-for-wordpress/comment-page-5/#comment-71666),
>> which allows to conduct DoS attack or reinstall of the engine (depending
>> on corrupted table). And in 2012 (http://websecurity.com.ua/5774/, on
>> English http://securityvulns.ru/docs27968.html) I wrote that developers
>> hadn't fixed it, even they said so, and they made new DoS vulnerability.
>>
>> In April 2012 I wrote my article "Attack via tables corruption in MySQL"
>> (http://lists.webappsec.org/pipermail/websecurity_lists.webappsec.org/2012-May/008363.html)
>> and in July made English version of the article
>> (http://websecurity.com.ua/articles/attack-via-tables-corruption-in-mysql/).
>> Where I described vulnerabilities in WordPress and IPB which are based
>> on my conception of attack via tables corruption.
>>
>> On Saturday I published a video with my WordPress DoS exploit
>> (http://www.youtube.com/watch?v=kwv5ni_qxXs), which shows this DoS
>> attack on one security site on WordPress. Vulnerable are all versions of
>> WordPress. This video is a proof of this vulnerability in WP and of the
>> attack described in the article.
>>
>> Best wishes & regards,
>> MustLive
>> Administrator of Websecurity web site
>> http://websecurity.com.ua
>>
>> _______________________________________________
>> Full-Disclosure - We believe in it.
>> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
>> Hosted and sponsored by Secunia - http://secunia.com/
>>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/