Greetings from, well, me? :P

In this little write up today, I am going to try and explain you what 'FPD' is, how to detect it, analyze it, and some pretty good methods of finding it in the wild.

/* Note that my write up was intended to PHP-based websites, but some of the methods works for ASP/ASPX too. */
/* I never imply myself to be an expert. If you see any mistakes - You know what to do! */

But first... The hell is FPD?

'FPD' (Stands for Full Path Disclosure) is one of the most common methods of attacks (While I doubt this kind of action categorized as a form of an attack, it is still a highly-related method of website security testing), that Pen-testers / Hackers / whatever use in order to gain an error which will expose the full installation path of the targeted site. 

Why is this happening?

By default (Don't quote me here. Some web-services and packages disable this function, but partly in most cases), the PHP error reporting function -

'1' = On. ==> 0 = Off.
Any kind of PHP error that happens when you load up a page will display itself on the page. That error is meant to notify the programmer about a coding glitch on his page.

The common error would basically look something similar to this -
The regular programmer would take in account everything, expect the full path, which does not interest him that much (Aside from the file name itself)... Unlike the intruder.

Now the question is: Why is the path needed?

Because, it is a must-have detail at some cases of those three attacks:

SQL Injection using load_file() & outfile

Those two SQL Queries (Also the 'dumpfile' query, so make it three) require the full path of the targeted directory in order to execute themselves.
Example:

Local File Inclusion (LFI)

Some variants of LFI attacks won't allow you to poison logs / use filters, so you can try loading your own way through the site. 

Symbolic linking (Symlinking) 

At some cases, when uploading a shell is not an option, you'd rather know the path in order to work a symbolic link - A shortcut.

And more methods which I can't come up with as for this moment.

So, How to cause it?

Oh, there's quite a few methods:

[#] Transforming X type of variables to type Y
Let's say 'err' is a number-y variable. It means, it could only $_GET numbers to it's related code.
Sooo... Try to insert a string instead. Might work.

[#] Using false file names Possible Output:
The script is including every kind name that goes through the $_GET, and prints the file under the requested name. Now, what will happen if we include a non-existing file?~

[#] Basically messing around with the value of the parameter
Sometimes, the value will be limited to only one style of inputs, and any kind of tweak would result a "Divided By Zero" PHP error.

[#] braces.
Well, it is messing up the parameter in a different way, so it's a different method xD
I believe this has something to do with the whole array usage at PHP (Uses braces?), not sure though.
Possible output:

[#] Messing around with the COOKIEZ
So, what did we just done?
Simple - We changed the value of the 'PHPSESSID' cookie (A default cookie name, found in probably-every-site-that-uses-cookies) into... Nothing. It becomes null.
Which, as you already guessed, fucks up something at the session:
You can try and edit other cookies of the site as well. In addition, you can also junk the cookie with illegal characters, and stuff like that.

[#] SQLi fuckery
Possible Output:
Creating an SQL data synthesizing error, which in result, will reveal us the asked FPD.
[#] Inner-library-files-thingie 
Traveling into inner files that has an undefined / defined twice functions will might result an output of the full FPD.

Other ways to get FPD, without coding errors.

[#] PHPINFO();
For some reason or another (Probably to often check the defined setting etc), some sites open a page with the php details. Well, we can use that~
Pic:
Look at the document root. ^_^

[#] '/etc/passwd' <- Default linux & FreeBSD categories-alike file. (Echos all the users of the box, their group number, and their installed path)
Because of the fact that a dedicated linux user was created for the web-service, obviously, his path will be visible on the site. Not always though, try to play smart here - Most of webservice users will be named after the domain / the domain itself.

[#] Google dorking
Pretty straight and simple. Insert your site, and look for any possible errors. You know what I like about Google? (Fuck, I like everything about it, but here's another reason), it also stores cache-pages, or, results-that-are-not-updated. You might find an error which was last week, but does not exist today at the same page

摘自 http://hi.baidu.com/evilrapper/blog/item/6924db27c6430023918f9d89.html