Peanut shell security vulnerability-vulnerability warning-the black bar safety net

2016-10-27T00:00:00
ID MYHACK58:62201680589
Type myhack58
Reporter 佚名
Modified 2016-10-27T00:00:00

Description

The official believes that this is not a vulnerability,I think the vulnerability is that you can use the target the peanut shell the user's network environment,and get the other peanut bar SN,reset,and then through the other method of entering their account number, and so on. Even cancel out the peanut shell assistant of the reset function. All of this,is SOCKS5 not set password caused. In addition the Linux password has been I crack,so.

!

Don't worry too much,I don't open any of the source code,not to attack anyone,just illustrate the problem.

First of all need to use libcurl or other similar tool,to obtain a bit which is opening a SOCKS5 proxy,and scan IP. Of course, to connect up,and then connect the other site for testing,so that it is secure. Such as my peanut bar where a server in 1 0 3. 4 4.., I scan it sure can scan out of my own. I just skip the scan some,mainly my own port emerged as the main,does not move someone else's stuff. And then my first scan to the list.

103.44.. Port:1 0 1 4 0 103.44.. Port:1 0 1 9 7 103.44.. Port:1 0 6 8 0 103.44.. Port:1 0 6 8 4 103.44.. Port:1 1 7 8 3 103.44.. Port:1 2 1 5 5 103.44.. Port:1 2 5 6 1 103.44.. Port:1 2 7 5 5 103.44.. Port:1 3 7 7 3 103.44.. Port:1 3 9 8 0 103.44.. Port:1 6 3 5 0 103.44.. Port:1 7 1 5 1 103.44.. Port:1 7 2 1 9 103.44.. Port:1 7 4 1 5 103.44.. Port:1 7 1 2 1 103.44.. Port:1 7 6 5 8 103.44.. Port:1 7 8 9 5 103.44.. Port:1 6 5 2 4 103.44.. Port:1 8 2 9 1 103.44.. Port:1 8 5 9 4 103.44.. Port:1 8 0 0 6 103.44.. Port:2 2 0 7 2 103.44.. Port:1 5 8 3 5 103.44.. Port:1 7 9 9 3 103.44.. Port:2 5 6 5 0 103.44.. Port:2 5 6 8 5 103.44.. Port:2 6 1 4 4 103.44.. Port:2 7 0 9 6 103.44.. Port:2 7 7 3 8 103.44.. Port:3 1 3 0 4 103.44.. Port:3 3 4 9 6 103.44.. Port:3 7 9 7 1 103.44.. Port:4 0 6 6 1 103.44.. Port:4 5 4 7 6 103.44.. Port:4 6 8 2 3 103.44.. Port:4 7 1 0 5 103.44.. Port:4 7 6 6 0 103.44.. Port:4 8 6 7 1 103.44.. Port:5 1 1 8 3 103.44.. Port:5 4 2 5 9 103.44.. Port:5 5 6 0 5 103.44.. Port:5 6 3 4 0 103.44.. Port:5 6 2 9 4 103.44.. Port:5 6 0 0 4 103.44.. Port:5 7 0 9 5 103.44.. Port:5 5 1 2 0 103.44.. Port:5 8 4 2 5 103.44.. Port:5 8 1 6 9 103.44.. Port:5 5 1 3 3 103.44.. Port:5 9 4 5 8 103.44.. Port:5 9 6 8 8 103.44.. Port:5 8 2 4 1

These are definitely a peanut shell,but not necessarily a peanut stick. I assume that the user of the routing is 1 9 2. 1 6 8. 1. x,of course, users may also is 1 9 2. 1 6 8. 0. x,we only make a guess. Of course there is my routing configuration. Then start to constantly access the http Protocol,1 6 0 6 2-port,see if can access. If it is,then re-test 4 4 0 2 2 port. This test method is also not open,anyway if it is a peanut shell,access 1 6 0 6 2 default returns the contents should be as follows.

!

Then 4 4 0 2 2 test.

!

Then use the account password to log on,the account until the password is cracked.

!

You can reset the entire route or how,anyway, this built-in account is yours,through him, to do a springboard for what to do,also is your,this time I'll end up.

The solution is simple, allow SOCKS5 proxy set the password.

Peanut shell security vulnerability