Well, they just keep coming out of the woodwork don’t they? Okay, bad metaphor to use woodwork in reference to the web. But you get the picture.
Yet another security flaw has been found in Chrome. Thank God it’s still in beta!
InformationWeek has published that a Vietnamese security company, Bach Khoa Internet Security (BKIS) has posted a proof of concept demonstrating how a long title and the SaveAs command in Chrome can create a buffer overflow and allow a hacker to remotely attack the computer and gain full control.
(And to all my Advanced PC Students….. what did I tell you about the buffer overflow problem??)
For those of you who don’t understand a word of what I just wrote in the explanation, here comes a Debbie explanation.
You’ve experienced a buffer overflow whether you realize what it was or not. Have you ever sent a BIG job to your printer and suddenly have it start printing out weird characters at the top of each page and just continued and continued and continued to keep printing these one line, three character pages? If so, you’ve experienced a buffer overflow on your printer!
This happens in programs when programmers fail to program into the code a way to handle too much data coming into it. We call this an “unchecked buffer” because the programming code doesn’t check or handle limits to the data it can hold.
Buffer overflows are so old and so well known it makes me sick to think that programmers are still not checking this in the code! It’s probably the most widely known method of hacking or exploiting there is. But I won’t go on one of my rants. That’s not what this is about.
Just wanted you to be aware that this is yet another reason not to be using this browser. And remember, it’s yet another Big Brother Browser disguised as nice, “do no harm” Google.












Recent Comments