Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Web-App-Sec
[Top] [All Lists]

Re: IIS Security

Subject: Re: IIS Security
Date: Mon, 21 Nov 2005 08:04:48 -0800
1) The traversal attacks used in the past, required running the
cmd.exe  file on the system partition. If your WWWROOT was on the
system partition, it was much easier to traverse to cmd.exe. It is
much harder if your WWWROOT is on a non-system partition.

2) Some of the attacks is the past assumed that the wwwroot was
c:\inetsdk\wwwroot so thesee attacks were successful. If the wwwroot
partition had been on a separate partition these attacks might have
failed.

3) It is much easier to control the permisssions for the anonymous
account (INETUSER) that IIS uses, if the WWWROOT is located on a
seperate partition.


On 11/21/05, Schmidt, Albert E <AES@ola.state.md.us> wrote:
If the default IIS account only has access to the root document, what is the 
harm of placing the root document on the same disk partition as the operating 
system?  If the account does not have access to the operating system files.




In Peace,
Saqib Ali
http://www.xml-dev.com/blog/
Consensus is good, but informed dictatorship is better.

<Prev in Thread] Current Thread [Next in Thread>