Chrome OS Remains Undefeated At Pwnium 3
hypnosec writes "Google has announced that its Chrome OS has managed to remain undefeated during the Pwnium 3 event that was held alongside Pwn2Own. Announced by Google on January 28, 2013 the Pwnium 3 event carried a prize money of $3.14 million. Researchers were asked to carry out attacks against a base Samsung Series 5 chromebook running the latest stable version of Chrome OS. It turns out security researchers were not able to come up with winning exploits even after the competition's deadline was extended. Google Chrome Team has revealed that partial exploit entries have been filled in but, no other details have been released."
The OS doesn't really do anything. It's a glorified web browser.
I'd be more impressed with OpenBSD not being hacked, and even that is essentially just an init process and sshd.
I mean Does chrome OS runs /have anything of value at all? all the data is kept on the server side. Most of the processing happens through browser. so if session is closed there is nothing of value left on the machine unless you re-login. Is that correct?
It only means that Chrome OS is not too badly engineered. As Chrome OS is pretty new, the number of people that had an in-depth look will be smaller. As it is quite a bit different from other OSes and offers a lot less functionality on the application side, other approaches may be required to crack it.
One could object to that that the kernel is still Linux. True, but the Linux kernel is one tough nut to crack. Even local exploits are in the vast majority not kernel-based, but some application messing up. If they are kernel based, it is typically a specific driver. I do not remember any remote exploits for the kernel at all in the last few years, except one in an exotic network protocol, and Chrome OS has no reason to enable anything in that class.
So while this is a good initial result, do not overvalue it. It is possible that Chrome OS gets broken in the next few years when people get more experience with it. Die to its limited functionality, it is also possible that it will remain very hard to break into or that nobody manages it. Personally, I would welcome a main-stream secure browsing solution establishing itself, but remember that you cannot do most things with Chrome OS that you can do with other OSes.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
Chrome OS is more barebones than my phone.
A router only to wifi to the Chrome OS and no active prevention measures (human intervention). If it's still standing securely after that time then I'll be impressed. Until then this is just great advertisement for the Chrome OS and nothing more.
To the best of my knowledge, Chrome OS doesn't listen on any ports out of the box. Even DMZing it would do nothing, because there's nothing for attackers to connect to. Perhaps you should learn more about Chrome OS before you come up with ideas like this.
Researchers is a broad term and the conditions kept many away.
Which explains why everything else there was broken, right? Nope, wait, also complete nonsense.
But what about off line? Google docs off line lets you edit documents and presentations off line. They sync when you get the connection. When it first came it had no off line edits. Then they have introduced doc and presentations. Spreadsheets would be next I guess. Or may be not. Gmail offline can be customized to keep last so many days worth of email in the local cache. Google calender works off line, ( I think, need to go back and check.).
Off line music player works, off line video play back works. Source of the media could be the internal drive or any USB drive, including the USB powered hard disks. Kindle off line reader works, three books cached very quickly. Apps exist like "Read this link later" that works off line.
So off line, you can watch video, listen to music, read books, cached web pages. You will have read/access to all the google drive docs. And write access to docs and presentations. I think for 200$ it is way more than what I expected.
sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
Chrome OS is prehacked. It comes installed with a trojan/bot which collects all your information and sends it to Google.
A major theme here is "it doesn't run many apps, that's why it's secure". Yeah, that must be it - it probably has absolutely nothing to do with the way they've implemented Mandatory Access Controls in a rigorous fashion, and the way they isolate resources with heavy use of cgroups, and the read-only root filesystem and tmpfs /tmp, and how they've made every binary use ASLR and NX and DEP, and how they've rewritten several major typically-vulnerable daemons to not run as root, and how they've developed userland daemons to broker access to hardware, and how they don't allow any files in user home dirs to be executables, or how they've started to sandbox device drivers, or the way they implemented separate processing stacks for HTTP and HTTPS, or how they verify not just the boot record but the whole boot stack and partition table and nv ram on every boot and and and ...
...
Yeah, all those things probably don't matter. They probably don't play any role in exploits that work on Windows-based Chrome failing on Chrome OS. It's not more inherently secure than any other OS, riiiggghhhhhttttt
"Ahh! I see you're in that indeterminate Schrodinger state where - oh, uh
.... did they hold the competition at the same time as pwn2own to ensure that the people who may be able to break it were otherwise engaged at a different event?
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.