Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Vuln-Dev
[Top] [All Lists]

Re: NOD32 Antivirus Long Path Name Stack Overflow Vulnerabilities

Subject: Re: NOD32 Antivirus Long Path Name Stack Overflow Vulnerabilities
Date: 23 May 2007 00:11:29 -0000
Although the vulnerabilities are hard to exploit, > it's not impossible.
There are some restrictions to bypass:

- The path name is formated in Unicode, so we have to find an opcode in an 
address with an unicode format
- The shellcode has to be in the path name so we have to use an Alphanumeric 
shellcode

What's to stop someone from encoding the path(shellcode) in unicode(using both 
bytes of unicode/no null bytes)? Also, is there a special situation why it has 
to be strictly alphanumeric? Because, in general this is not the case.

I've worked with these guidelines myself in the 
past(http://fakehalo.us/xfinder-ds.pl), and I see no specific issue with doing 
similar for this, unless information to the contrary isn't included.

<Prev in Thread] Current Thread [Next in Thread>