Anatomy of a hack: 6 separate bugs needed to bring down Google browser
1–10 of 16 posts
Re: Anatomy of a hack: 6 separate bugs needed to bring down Google browser
#2The article makes it sound like since "6 separate bugs" were needed to bring down Chrome, it proves that its a more secure browser (than presumably IE or Firefox). But in 10 days a teenager found 6 bugs in Chrome in 2012? That doesn't sound more secure.
Re: Anatomy of a hack: 6 separate bugs needed to bring down Google browser
#3The article makes it sound like since "6 separate bugs" were needed to bring down Chrome, it proves that its a more secure browser (than presumably IE or Firefox). But in 10 days a teenager found 6 bugs in Chrome in 2012? That doesn't sound more secure.
It's probably easier to find bugs the deeper you get. There's the assumption that you're authorized, and fewer people get that deep so exploits come up less. It's far from ideal, but most of the issues are listed as low (2) or medium (2). Only one is listed as high (though the last is undisclosed).
Re: Anatomy of a hack: 6 separate bugs needed to bring down Google browser
#4The article makes it sound like since "6 separate bugs" were needed to bring down Chrome, it proves that its a more secure browser (than presumably IE or Firefox). But in 10 days a teenager found 6 bugs in Chrome in 2012? That doesn't sound more secure.
Yes, "Teen pwns Chrome in 10 days, how long will it take China?" can easily be the headline.
Re: Anatomy of a hack: 6 separate bugs needed to bring down Google browser
#5The scary part was the limitation that hackers weren't allowed to exploit Windows vulnerabilities. When you think of how many unpatched Windows 7 (or older) machines are out there it's no wonder botnets keep growing..
Re: Anatomy of a hack: 6 separate bugs needed to bring down Google browser
#6The article makes it sound like since "6 separate bugs" were needed to bring down Chrome, it proves that its a more secure browser (than presumably IE or Firefox). But in 10 days a teenager found 6 bugs in Chrome in 2012? That doesn't sound more secure.
This isn't just any teenager but I get your point. Maybe it's easier to find bugs because they have access to the source code?
Re: Anatomy of a hack: 6 separate bugs needed to bring down Google browser
#7The scary part was the limitation that hackers weren't allowed to exploit Windows vulnerabilities. When you think of how many unpatched Windows 7 (or older) machines are out there it's no wonder botnets keep growing..
I thought the scary part was the pink my-little-pony wielding a battle-axe that Pinkie Pie chose as his ("his?" ... i assume) mascot. ;) But then, different things scare different people different ways, and maybe I've just become numb the Windows-scare already.
Re: Anatomy of a hack: 6 separate bugs needed to bring down Google browser
#8The scary part was the limitation that hackers weren't allowed to exploit Windows vulnerabilities. When you think of how many unpatched Windows 7 (or older) machines are out there it's no wonder botnets keep growing..
[deleted]
Re: Anatomy of a hack: 6 separate bugs needed to bring down Google browser
#9The scary part was the limitation that hackers weren't allowed to exploit Windows vulnerabilities. When you think of how many unpatched Windows 7 (or older) machines are out there it's no wonder botnets keep growing..
I thought the scary part was the pink my-little-pony wielding a battle-axe that Pinkie Pie chose as his ("his?" ... i assume) mascot. ;) But then, different things scare different people different ways, and maybe I've just become numb the Windows-scare already.
Actually, that "pink my-little-pony wielding a battle-axe"-pony is Pinkie Pie (http://mlp.wikia.com/wiki/Pinkie_Pie) ;)
She's known for being able to break the fourth wall (unlike the other ponies in FiM) and doing other "impossible" things, which I'm figuring the hacker may have connected to breaking out of a sandbox.
You may also want to see: https://secure.wikimedia.org/wikipedia/en/wiki/My_Little_Pon...
Re: Anatomy of a hack: 6 separate bugs needed to bring down Google browser
#10The scary part was the limitation that hackers weren't allowed to exploit Windows vulnerabilities. When you think of how many unpatched Windows 7 (or older) machines are out there it's no wonder botnets keep growing..
How many unpatched Windows 7 boxes are there? Do you have any numbers. I thought automatic updates were enabled by default on them.