It actually doesn't work.... at.exe is a protected command.
However, the guy published his findings here:
http://www.pandora-security.com/foru...pic.php?t=2093
I find it odd that he didn't include what version of XP he was using(read: service pack level)
Instead he makes this statement:
Quote:
-[2.1] Getting SYSTEM
I will now walk you through the process of obtaining SYSTEM privileges.
To start, lets open up a command prompt (Start > Run > cmd > [ENTER]).
At the prompt, enter the following command, then press [ENTER]:
Code:
at
If it responds with an "access denied" error, then we are out of luck, and you'll have to try another method of privilege escalation; if it responds with "There are no entries in the list" (or sometimes with multiple entries already in the list) then we are good.
|
I find this explaination odd, as it truly doesn't make sense. Why would you get an access denied vs. access granted on a standard installation?
I just tested with a local user account and a domain account on a Windows XP SP2 laptop, no dice.
Hrmmm I will keep trying to gather info.