I have recently read the news about Google Chrome Buffer Overflow vulnerability (see this link). Admittedly, I was ignorant enough not to understand how a buffer overflow can cause severe security breaches! Wikipedia came to the rescue, as well as some research into the topic of Assembly-language programming. At last I can understand how SEVERE such an attack could be!
You can dig for it too ;-)
check the Wikipedia article,
http://en.wikipedia.org/wiki/Buffer_overflow
and the excellent book of Programming from the Ground Up, for much better understanding of Assembly:
http://savannah.nongnu.org/projects/pgubook/
Enjoy!
Popular Posts
-
Today I tried to compile and install the WFDB tools from the PhysioToolkit ( PhysioNet ) on my Debian Squeeze system. I am documen...
-
http://blog.akkaya.de/blojsom/blog/jpabel/
-
It took me some long time to comprehend the issues involved in using unions, structs, and bit fields in C and C++. First, for the definition...
-
Trying to install Ubuntu 12.04 on Dell Vostro 470 gave me all kinds of trouble! At first, the graphical installer did NOT work, so I had to...
-
I have been searching for open source tools to assist in detecting memory leaks and application profiling. Also, static code analysis was an...
Saturday, September 27, 2008
Wednesday, September 3, 2008
Subscribe to:
Posts (Atom)