|
|||||||||||
|
RE: NSLOOKUP.EXE
From: Brett Moore <brett(at)softwarecreations.co.nz>
Date: Sun Mar 23 2003 - 16:41:23 EST
On win32 systems, it is a common misconseption that buffer overflows in
local executables through
However they do give an attacker another avenue of attack. For example.
going back to the long unicode/double decode vulnerabilities where one
simple solutions was
But with the help of a local exe that is vulnerable to command line
overflow, couldnt an attacker
Brett
-----Original Message-----
Hi, On a related note, we had reported the following local BOs to MS. But since, neither they nor us could come up with any remote exploits for this, I guess members on this list could check it out. Some of these do not work on Win2K SP3, but do work on earlier versions.
First:
Second:
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaa.exe This one crashes only at a particular value of A's, not if its any more or if its any less. Again, unless any of these runs with elevated privileges, or someone feeds in data remotely to these exes, the buffer overflows do not represent a security risk.
K. K. Mookhey
Security Auditing Handbooks http://www.nii.co.in/research/handbook.html
Can you do anything interesting with this?:
C:\>nslookup
>
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA Gives error: memory can't be "read" - 0x414141 (aka A). Received on Sun Mar 23 22:23:32 2003 This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 14:07:38 EDT |
||||||||||
|
|||||||||||