| 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
| ||
|
Message-ID: <20130119191012.GB2850@kludge.henri.nerv.fi> Date: Sat, 19 Jan 2013 21:10:12 +0200 From: Henri Salo <henri@...v.fi> To: MustLive <mustlive@...security.com.ua> Cc: full-disclosure@...ts.grok.org.uk Subject: Re: Wordpress Pingback Port Scanner On Sat, Jan 19, 2013 at 08:53:24PM +0200, MustLive wrote: > And when WordPress developers turned in on in WordPress 3.5 they returned > the hole back to the masses. Earlier for WP 2.6 - 3.4.2 only those web sites > were vulnerable, which had turned it on, then since WP 3.5 all web sites > would be vulnerable again. First of all I am impressed that you MustLive have studied this issue so much and given valuable information to this mailing list. Thank you. I'll bet you can give lot to the community if you start to find vulnerabilities from important software and don't waste time to non-issues (not saying that you haven't done this already in some level). Could you give me references where WordPress developers enabled XML-RPC again? In my opinion this is not wise decision. The interface should have at least some kind of ACL enabled. I have no idea what is now allowed or is there possibility to configure the interface. Last time I tested this interface it did need authentication to do some of the tasks. I did not check all of them. - Henri Salo _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
Powered by blists - more mailing lists