BugTraq
Re: DotClear Full Path Disclosure Vulnerability Feb 13 2007 05:47AM
Cedric Blancher (blancher cartel-securite fr) (1 replies)
Re: DotClear Full Path Disclosure Vulnerability Feb 13 2007 07:34AM
Raphaël HUCK (raphael huck free fr) (1 replies)
>> 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?

[ reply ]
Re: DotClear Full Path Disclosure Vulnerability Feb 13 2007 09:10AM
Cedric Blancher (blancher cartel-securite fr) (1 replies)
Re: DotClear Full Path Disclosure Vulnerability Feb 13 2007 06:57PM
Gmail account (god ate my homework gmail com) (2 replies)
Re: DotClear Full Path Disclosure Vulnerability Feb 14 2007 09:06AM
Cedric Blancher (blancher cartel-securite fr)
Re: DotClear Full Path Disclosure Vulnerability Feb 13 2007 09:39PM
Raphaël HUCK (raphael huck free fr)


 

Privacy Statement
Copyright 2010, SecurityFocus