Forgot your password?

typodupeerror
Google Security Technology

Chrome OS Remains Undefeated At Pwnium 3 178

Posted by timothy
from the technical-victory dept.
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."
This discussion has been archived. No new comments can be posted.

Chrome OS Remains Undefeated At Pwnium 3

Comments Filter:
  • by CannonballHead (842625) on Friday March 08, 2013 @08:38PM (#43122659)
    From what I understand, there are, at the very least, local caches (similar to Google Drive/Docs/Email offline). Also, there would be all the info that Chrome keeps locally.
  • by dreamchaser (49529) on Friday March 08, 2013 @10:08PM (#43123259) Homepage Journal

    Typical geek-elitist drivel. For some (myself included) sure it's important to understand the nature of how computers do things. What you seem to fail to see, or are in denial about, is that computers have become ubiquitous appliances, and the average user doesn't give a shit about the 'nature of how we do these things.' They just want it to work.

  • by amiga3D (567632) on Friday March 08, 2013 @10:14PM (#43123287)

    Yes. Most people don't even have a clue how the light in their room comes on when they flip the switch and could care less about electricity as long as when they flip the switch the light comes on. Almost no one knows anything about internal combustion that drives a car daily they just know that when you turn the key it should start. The how and why is beyond them. Computers are even more complex to these people and it's crazy to think they'll ever know or care how they work.

  • by gman003 (1693318) on Saturday March 09, 2013 @12:21AM (#43123827)

    The difference is that Chrome OS is a consumer-grade "thin client". It is aimed mainly at home and educational use, not the big corporate or government use most other thin clients aim for.

    As such, yes, it makes sense to compare it to other consumer-grade operating systems. The results won't be quite comparable, as many duties normally handled by the OS are done remotely, in "the cloud", but it's still a worthwhile comparison.

  • by daboochmeister (914039) <[moc.liamg] [ta] [retsiemhcoobad]> on Saturday March 09, 2013 @01:05AM (#43123971)
    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 ...
  • by Anonymous Coward on Saturday March 09, 2013 @01:37AM (#43124089)

    Look under the hood. Chrome OS is just as capable of running X11 apps as your off the shelf distro. Granted, it's not designed to so it's difficult to make it do so, damn near impossible (as seen in article) without switching developer mode on.

    But, switch developer mode on, turn off rootfs verification, remount as RW, and dump binaries on that it'll happily run. I don't typically categorize thin clients as a system running GNU/Linux w/ X11 support.

    I think the ace in the hole for ChromeOS security is that any partitions writable are mounted noexec. Any partition mounted exec, is read only. How do you get around that without attacking the kernel itself?

Guillotine, n.: A French chopping center.

Working...