bugtraq - Re: Path Disclosure

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] [day] [month] [year] [list]

Date: Tue, 27 Mar 2007 10:12:17 +1000
From: jm <jm@....com.au>
To: bugtraq@...urityfocus.com
Subject: Re: Path Disclosure  - Wordpress 2.1.2

"All sites"? That's a bit of a stretch. Maybe you should rephrase that
to "All sites with 'display_errors = On'" in their php.ini, which by the
way is disabled in php.ini-recommended in 4.4.6 and 5.2.1.

There's even a comment in php.ini* about it:

"Print out errors (as a part of the output).  For production web sites,
you're strongly encouraged to turn this feature off, and use error
logging instead (see below).  Keeping display_errors enabled on
a production web site may reveal security information to end users,
such as file paths on your Webserver, your database schema or other
information."

--jason

lj@...jectzero.net wrote:
> Product : Wordpress 2.1.2
> Vulnerability Details :
> All the sites running on the latest version of wordpress 2.1.2 are exposed to a full path disclosure vulnerability.
> 
> Proof of Concept:
> http://www.anysite.com/Path_to_wordpress/wp-includes/vars.php
> 
> Error Returned:
> 
> Fatal error: Call to undefined function get_option() in /home/santoshp/public_html/wp-includes/vars.php on line 92
> 
> Location:
> www.indiaesecure.com/exploits.htm/wp212.txt
> 
>