02.03.2018 Views

Sybex CEH Certified Ethical Hacker Version 8 Study Guide

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

170 Chapter 7 ■ Gaining Access to a System<br />

■<br />

■<br />

■<br />

■<br />

Let’s take a look at some of the commands you can use with PsExec:<br />

The following command launches an interactive command prompt on a system named<br />

\\zelda: psexec \\zelda cmd.<br />

This command executes ipconfig on the remote system with the /all switch, and displays<br />

the resulting output locally: psexec \\zelda ipconfig /all.<br />

This command copies the program rootkit.exe to the remote system and executes it<br />

interactively: psexec \\zelda -c rootkit.exe.<br />

This command copies the program rootkit.exe to the remote system and executes it<br />

interactively using the administrator account on the remote system: psexec \\zelda<br />

-u administrator -c rootkit.exe.<br />

As these commands illustrate, it is possible for an attacker to run an application on a<br />

remote system quite easily. The next step is for the attacker to decide what to do or what<br />

to run on the remote system. Some of the common choices are Trojans, rootkits, and<br />

backdoors.<br />

Other utilities that may prove helpful in attaching to a system remotely are the<br />

following:<br />

PDQ Deploy This utility is designed to assist with the deployment of software to a single<br />

system or to multiple systems across a network. The utility is designed to integrate with<br />

Active Directory as well as other software packages.<br />

RemoteExec This utility is designed to work much like PsExec, but it also makes it easy to<br />

restart, reboot, and manipulate folders on the system.<br />

DameWare This is a set of utilities used to remotely administer and control a system.<br />

Much like the other utilities on this list, it is readily available and may not be detected by<br />

antivirus utilities. DameWare also has the benefit of working across platforms such as Windows,<br />

OS X, and Linux.<br />

Covering Your Tracks<br />

Once you have penetrated a system and installed software or run some scripts, the next<br />

step is cleaning up after yourself or covering your tracks. The purpose of this phase is to<br />

prevent your attack from being easily discovered by using various techniques to hide the red<br />

flags and other signs. During this phase, you seek to eliminate error messages, log files, and<br />

other items that may have been altered during the attack process.<br />

Disabling Auditing<br />

One of the best ways to prevent yourself from being discovered is to leave no tracks at all.<br />

And one of the best ways to do that is to prevent any tracks from being created or at least<br />

minimize the amount of evidence. When you’re trying not to leave tracks, a good starting<br />

point is altering the way events are logged on the targeted system.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!