Home page logo

fulldisclosure logo Full Disclosure mailing list archives

Re: Question for the Windows pros
From: Nicolas RUFF <nicolas.ruff () gmail com>
Date: Thu, 19 Jan 2006 10:32:44 +0100


The ImpersonateNamedPipeClient() risks have been fully documented by
Blake Watts back in 2002.

The problem is basically that OpenFile() will accept either :
- A file path ("C:\toto.txt")
- A share path ("\\hacker\toto")
- A named pipe path ("\\hacker\pipe\toto")

(Did you ever notice that you cannot create a share named "pipe" on a
Windows system ? ;)

So if you can open a file with a privileged application (such as a
SYSTEM service), you can gain the privileges of the application.

Real life example: take your antivirus, change the log file name from
"C:\Program Files\Antivirus\log.txt" to "\\mycomputer\pipe\toto" while
running a listener on the "toto" pipe. When the antivirus opens the log
file, you become SYSTEM.

- Nicolas RUFF
Security Researcher @ EADS-CRC
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/

  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]