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 had the opportunity to attend a session given by Dr. Moustafa Youssef on his research. The key point in his talk was about detectin...
-
From the gcc man page: -dCHARS CHARS is a sequence of one or more of the following characters, and must not be preceded by a spac...
-
I spent a scary night yesterday trying to fix my Ubuntu installation. I was a victim for the bug related to libc6. The problem is that afte...
-
In 1975 Widrow et. al. introduced a scientific paper about Adaptive Noise Cancellers (ANCs). Since then, ANCs have been used extensively in...
-
Recently I needed to add a header/footer to an existing PDF file. With some help from this link, I figured it out: http://coding.derkeiler.c...
Saturday, September 27, 2008
Wednesday, September 3, 2008
Subscribe to:
Posts (Atom)