full-disclosure - Re: WordPress User Account Information Leak / Secunia Advisory SA23621

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <51D579FA.7070701@dxw.com>
Date: Thu, 04 Jul 2013 14:34:50 +0100
From: Harry Metcalfe <harry@....com>
Cc: security@...dpress.org, full-disclosure@...ts.grok.org.uk, vuln@...unia.com
Subject: Re: WordPress User Account Information Leak /
 Secunia Advisory SA23621

There have been many heated debates within the community about this 
issue. Unfortunately, I think a different outcome is unlikely.

WordPress's position is (I think) that usernames aren't secret, and that 
therefore, username enumeration is a non-problem. I think this is 
extremely wrong, but it is what it is.

We solve this problem with a plugin that changes the login messages and 
ensures that invalid usernames will prepopulate the form, as well as 
valid ones.

We also look for [?|&]a=\d in the URL and remove any matches before the 
request hits apache, so that attackers can't run through ?a=1, ?a=2 etc 
looking for redirects to author pages (which include usernames in the URL_.

I've attached the relevant code, but it would need a little work in 
order to run outside our infrastructure. It is a bit fragile, and would 
need to be changed if WordPress's login errors changed - currently, 
there is not a more robust way to do it, as far as we know. Feedback 
welcome if anyone knows of a better way!

Harry
http://security.dxw.com

On 04/07/13 14:22, Ivan Carlos wrote:
>
> Can't you open a new bt about this issue?
>
> Regards,
>
> Em 04/07/2013 10:16, "Sven Kieske" <svenkieske@...il.com 
> <mailto:svenkieske@...il.com>> escreveu:
>
>     Hi,
>
>     the mentioned User account Enumeration Weakness
>     stated in Advisory https://secunia.com/advisories/23621/
>     still exists in the actual version 3.5.2 .
>
>     The corresponding trac entry for wordpress is closed as
>     "wontfix":
>     https://core.trac.wordpress.org/ticket/1129
>
>     Why?
>
>     Maybe, because the trac bug mentions just version 1.5 as affected?
>
>     I can easily reproduce this in version 3.5.2 .
>
>     Please fix this, this bug is 8 years old!
>
>     Kind Regards
>
>     Sven Kieske
>
>     _______________________________________________
>     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/

Content of type "text/html" skipped

Download attachment "login_errors.class.php" of type "application/x-php" (1699 bytes)

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