bugtraq - Re: DotClear Full Path Disclosure Vulnerability

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]

Date: Tue, 13 Feb 2007 08:34:02 +0100
From: Raphaël HUCK <raphael.huck@...e.fr>
To: Cedric Blancher <blancher@...tel-securite.fr>
Cc: bugtraq@...urityfocus.com
Subject: Re: DotClear Full Path Disclosure Vulnerability

>> They should check that a certain variable is defined for example, and if 
>> not, do not display anything... even if the hosted website is configured 
>> to display errors, and you cannot change this.
> 
> Exactly my point: you may not have the choice of your PHP configuration.

I said I agreed with you. But you can use secure software (or modify the 
unsecure ones you have), so that they don't enable a full path 
disclosure, even if you don't have the choice of your PHP configuration! 
Can't you? ;)

> Note that checking a variable is set may note be the best solution as
> attacker can provide it as well ;)

I said "for example", as I know this is how MediaWiki does:

if ( ! defined( 'MEDIAWIKI' ) )
     die( 1 );

How would you do it?