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
-
http://blog.akkaya.de/blojsom/blog/jpabel/
-
Sometimes you have to deal with the .Net framework in a way or another. I was forced to use a .Net C# closed-source library. And that librar...
-
In this post I will be gathering some links about the physiological signals datasets that are publicly available on the web. This post will ...
-
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...
-
In 1975 Widrow et. al. introduced a scientific paper about Adaptive Noise Cancellers (ANCs). Since then, ANCs have been used extensively in...
Saturday, September 27, 2008
Wednesday, September 3, 2008
Subscribe to:
Posts (Atom)