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
-
Debian 5.0 (codenamed "Lenny") is out. Check: http://www.desktoplinux.com/news/NS4199843436.html It appears that Debian 5.0 (aka ...
-
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...
-
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...
-
Bugzilla is a great project. Yet, customizing it to your needs is an overwhelming task! I was assigned a task that our Bugzilla server shoul...
-
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...
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment