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?
Have zero surface! (Apologies for the redundancy.. OS that does nothing jokes have already been cracked.. couldn't resist adding my own :P)
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.
Or at least the Chrome OS developers could give the Android developers a few pointers...
http://tech.fortune.cnn.com/2013/03/07/apple-android-malware/
Chrome OS is more barebones than my phone.
Android is fairly secure (again, the base OS doesn't do much.) The mentality around apps is what's wrong.
There must exist a way to disable permissions on a per application basis, but Google will not allow it when it would kill search revenue. People must stop installing apps that access permissions they don't need, but they won't so long as they want their free app toys.
I wonder what will happen in another 15 years. When the "win95 generation" moves in to upper management and the "relatively virus free win7/osx generation" starts designing and managing their own pay-software.
The current crop of software devs dealt with stuxnet, *worm and all that other crap. They probably dealt with it on their parent's computers, their grand parents and neighbors. Designing secure, web connected software is in their interests.
Will the next generation of developers who entered middle school with facebook already being a thing have the same security concerns? People who survived the Great Depression are typically much more fiscally savvy than those born in the credit era of the 80s 90s and early 2000s.
Does this mean we're going to plunge in to a security trough as mediocre corporate software developers push out crap, insecure code, not knowing how insecure code causes problems down the road?
moox. for a new generation.
OMFG MALWARES! sigh ...
https://play.google.com/store/apps/details?id=com.fsecure.ms.dc&hl=en
that's f-secure's (the authors of the report) mobile app that costs $10.58. you think it's just coincidence that it's always someone with a product to sell that's behind these reports?
You could build a really nice server with the $1,100 left over after buying a $199 Acer Chromebook. A Pixel in this paradigm is the dick to the balls.
Uhm, I will.
I don't give permission for shit to shit. I barely even give permission to my ass for shitting.
Seriously though, if I install something, it is either:
1. A commercial app made by a well known company (Doesn't guarantee it's secure, but it's probably not malware)
2. An open source program. (The person who compiled it could be evil though I suppose and have inserted his own special code to do whatever.. but it would need permissions that are suspicious).
In all seriousness, I don't get though why some people think that basic shit should be commercial or full of ads just because it's "mobile". Basic shit like FTP, calculator programs, SSH, VNC, etc. should be available for free by now. Just because the OS is new doesn't make these things groundbreaking. I really wish Google would take a stab at these basic apps in order to kill the overpriced commercial leaches and get rid of the ad infested junkware (I know they make money from ads, but there is such a thing as too junky).
Well actually they could, all they have to do is to allow http(s) access to the adds-network (or a whitelist) and allow the user to deny everything else.
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
Apparently Safari also hasn't been hacked. Odd that it wasn't mentioned...
Chrome OS is prehacked. It comes installed with a trojan/bot which collects all your information and sends it to Google.
I read the title as "Chrome OS Remains Undefeated On A Pentium 3".
That would have been more interesting!
What could possibly hurt the security of the American people more than giving our own government the ability to hide its
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
I think the kids going through middle school now will be fine. When i was a kid there was no such thing as malware or fishing. It was worms and viruses. Spam was so rare that filters didn't exist. We didn't have wifi and didn't have to worry about wardrivers. The internet wasn't something you could carry in your pocket. We didn't have social media, we had Geocities.
I agree with you that their concerns will be different. But i don't think it will lead to completely insecure programming.
http://soylentnews.org/~tibman
So Chrome will show my what Google wants me to see much faster than Firefox will show me what I want to see.
I've calculated my velocity with such exquisite precision that I have no idea where I am.
.... 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.
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.
The rules call for wifi access only to the Chrome OS the router is to connect to that wifi from the outside.
That it's secure according to this headline.... which doesn't make sense at all, it's arguing that security by obscurity works... and it doesn't... Period
Any and all content posted above may be ignored, considered irrelevant, or otherwise dismissed.
Let's see how well Chrome OS does next year after it's been released to the public for a while.
These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
First of all, I'm not sure exactly what you're saying. That being said, my point is that opening it up to the world (which is the most extreme option) wouldn't do anything, because there's no way for attackers to get in. The rules specifically allow the attackers to specify a website that will be navigated to. So leaving a Chrome OS laptop just sitting there won't do anything, because there's no way for attackers to get in; you're going to have to go to an attack page of some sort.
it's arguing that security by obscurity works
Spoken by someone who doesn't know what they are talking about.
All encryption and digital signatures are security through obscurity. All RSA hardware tokens, all passwords, all digital signatures including your precious PGP keys ... all security through obscurity.
In fact ALL computer security is security through obscurity at this stage unless that security happens to be something like 'bury it in 2000 meters of concrete.
Stop repeating things you don't understand.
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager