Server|web
This paper mainly describes the safety of Asp/iis and its corresponding countermeasures, do not advocate the use of the method mentioned in this article to do any damage, otherwise the consequences of the invasion of the Web server through ASP, theft of files destroyed the system, this is not sensational ...
Security issues with IIS
1.IIS3/PWS's vulnerability
I have experimented, WIN95+PWS running ASP program, only in the browser address bar add a small dot ASP program will be downloaded down. IIS3 heard that the same problem, but I did not try to come out.
2.IIS4 's vulnerability
IIS4 a well-known vulnerability is:: $DATA, is the ASP's URL after adding these characters, the code can also be seen, using IE view source can see the ASP code. Win98+pws4 doesn't have that problem. There are several solutions, one is to set the directory is not readable (ASP can still execute), so that the HTML file can not be placed in this directory, otherwise HTML can not browse. The second is to install the patch program provided by Microsoft. The third is to install IE4.01SP1 on the server.
3. The problem of supporting ASP's Free home page Your ASP code may be available to people. ASP1.0 's example has a file to view the ASP's original code,/aspsamp/samples/code.asp
If someone put this program up, he can check other people's programs.
For example: code.asp?source=/someone/aaa.asp
The Access database you use may be downloaded since the ASP program can be people get, others can easily know where your database is placed and download it, if the database contains passwords not encrypted, that ... It's dangerous. Webmaster should take certain measures, strictly prohibit the code.asp such programs (seemingly difficult to do, but can regularly retrieve the signature code), limit the MDB download (do not know do not do)
4. IIS4 from the FileSystemObject of the ASP's file operations can be implemented through FileSystemObject, including text file read and write directory operations, file copy renamed Delete, etc., but this dongdong is also very dangerous. Using Filesystemobjet can tamper with downloading any file on a FAT partition, even NTFS, if the permissions are not set well, it can also destroy, unfortunately many webmaster only know that the Web server to run, very little NTFS permissions settings. For example, a Web server that provides virtual hosting services, if permissions are not set, users can easily tamper with deleting any file on the machine, or even let NT crash. Program refer to Active Server Explorer on http://www.pridechina.com/chinaasp/, which can browse all files and directories of the unprotected Web server.
Webmater The web directory should be built on an NTFS partition, not the web directory, not the Everyone control, but the administrator.