[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: HTB22905: Path disclosure in Wordpress
My point-of-view is that anything can be made "insecure". The
WordPress issue is avoidable by just configuring the server to common
standards of not displaying errors in a production environment. That
seems pretty simple. I can see instances where I would want the
software to reveal the path if needed to troubleshoot a WP instance.
That can be done in a controlled test environment by allowing errors
to be displayed through PHP.
Removing functionality to get around configuring the environment
properly seems counterproductive.
The Simple PHP Newsletter vulnerabilities from yesterday are a
highlight of the same thing. Follow the instructions and remove the
install directory. This is not an exploit or vulnerability in the
software, either. Those directories are required to be there to
install and upon finishing installation, you remove them. Problem
The Ubuntu releases in the last couple of days are actual software
issues in my opinion, not just poorly configured environments.
On Wed, Mar 30, 2011 at 11:32 AM, Christian Sciberras <uuf6429@xxxxxxxxx> wrote:
> I disagree. It is definitely a software issue.
> I just can't waste time with this, so I'll highlight a quick example;
> Firefox (as a clear example) comes with the right security dialogs
> enabled, even if you can later on tell it to always open exe files
> after download.
> The same can't be said for Wordpress, where it comes vulnerable by
> default. By the same reasoning, why does Wordpress ask for a user
> password during install? Why not a default one (and then tell people
> to change it in the manual)?
> Keep in mind I'm not viewing this from a pure security perspective;
> I'm foremost a software developer, not security specialist, and I see
> it good practice to build on solid practices.
> As to the watch analogy, I'm not sure I get it.
> On Wed, Mar 30, 2011 at 5:22 PM, Patrick Kelley <psworn@xxxxxxxxx> wrote:
>> Seems like most of the "vulnerabilities" from the last couple days are
>> not actual software issues, but problems with configuration of the
>> server or just not following the directions provided by the vendor.
>> If that is our measure for vulnerability, I can show about 10 for the
>> wristwatch I am wearing...
>> On Tue, Mar 29, 2011 at 11:42 AM, Christian Sciberras <uuf6429@xxxxxxxxx> wrote:
>>> Ridiculous! I've been talking about this for some time, the actual
>>> list of vulnerable files follows:
>>> That's some 30%-40% of all Wordpress files (depending on Wordpress install).
>>> I considered making this public but...
>>> Read the 5th clause.
>>> On Tue, Mar 29, 2011 at 11:55 AM, <advisory@xxxxxxxxxxx> wrote:
>>>> Vulnerability ID: HTB22905
>>>> Reference: http://www.htbridge.ch/advisory/path_disclosure_in_wordpress.html
>>>> Product: Wordpress
>>>> Vendor: http://wordpress.org/ ( http://wordpress.org/ )
>>>> Vulnerable Version: 3.1
>>>> Vendor Notification: 15 March 2011
>>>> Vulnerability Type: Path disclosure
>>>> Status: Not Fixed
>>>> Risk level: Low
>>>> Credit: High-Tech Bridge SA - Ethical Hacking & Penetration Testing (http://www.htbridge.ch/)
>>>> Vulnerability Details:
>>>> The vulnerability exists due to failure in the "/wp-includes/theme-compat/" & "/wp-content/themes/twentyten/" scripts, it's possible to generate an error that will reveal the full path of the script.
>>>> A remote user can determine the full path to the web root directory and other potentially sensitive information.
>>>> The following PoC is available: