본문 바로가기

Redis2

728x90
Redis 서버 제어권 심각한 취약점 존재 服务器配置不当包括三个部分: 1.Redis服务使用ROOT账号启动 2.Redis服务无密码认证或者使用的是弱口令进行认证 3.服务器开放了SSH服务,而且允许使用密钥登录简单的写下过程测试环境 victim server CentOS6.6 192.168.1.11 attack server CentOS6.6+redis2.4 192.168.1.1212345678910$ telnet 192.168.1.11 6379Trying 192.168.1.11...Connected to 192.168.1.11.Escape character is '^]'.echo "Hey no AUTH required!"$21Hey no AUTH required!quit+OKConnection closed by foreign host.表明了Redis是正常工作的.. 2015. 11. 18.
728x90

服务器配置不当包括三个部分:
1.Redis服务使用ROOT账号启动
2.Redis服务无密码认证或者使用的是弱口令进行认证
3.服务器开放了SSH服务,而且允许使用密钥登录

简单的写下过程

测试环境
victim server CentOS6.6 192.168.1.11
attack server CentOS6.6+redis2.4 192.168.1.12

表明了Redis是正常工作的,而且不需要进行身份认证。

先在attack server生成一个公钥

这样有了一个公钥,但是需要把这个公钥复制到目标机器

Now foo.txt is just our public key but with newlines. We can write this string inside the memory of Redis using redis-cli:

Looks good. How to dump our memory content into the authorized_keys file? That’s
kinda trivial.

At this point the target authorized keys file should be full of garbage, but should also include our public key. The string does not have simple patterns so it’s unlikely that it was compressed inside the RDB file. Will ssh be so naive to parse a totally corrupted file without issues, and accept the only sane entry inside?

参考:
http://antirez.com/news/96
http://v2ex.com/t/234520#reply25



출처 : 0day5.com

728x90
728x90