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
-
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...
-
From the Chinese Linux University! http://www.chineselinuxuniversity.net/articles/13049.shtml Add to /etc/X11/xorg.conf (or whatever your xo...
-
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...
-
I found this interesting post, quoting: apt-get build-dep glibc apt-get source -b glibc should work or, if you already have the build-depen...
-
I just installed a new Fedora 17 system to get familiar with it. Now I am trying to install the brand new ROS Fuerte on this Fedora system ...
Saturday, September 27, 2008
Wednesday, September 3, 2008
Subscribe to:
Comments (Atom)