Palm WebOS Hacked Via SMS Messages 99
gondaba writes "Security researchers at the Intrepidus Group have hacked into Palm's new WebOS platform, using nothing more than text messages to exploit a slew of dangerous web app vulnerabilities. The white hat hackers found that the WebOS SMS client did not properly perform input/output validation on any SMS messages sent to the handset, leading to a rudimentary HTML injection bug. Coupled with the fact that HTML injection leads directly to injecting code into a WebOS application, the attacks made possible were quite dangerous (especially considering they could all be delivered over an SMS message)."
Lol (Score:2, Funny)
Re: (Score:2)
Re:Lol (Score:5, Insightful)
Re: (Score:2, Insightful)
its really not that hard to write protective measures for, of all things, input validation. thats literally day 3 material in any intro web programming class these days.
Re: (Score:2, Funny)
Re: (Score:1, Funny)
Re: (Score:2)
Re:Lol (Score:0) ... including this post.
by Anonymous Coward writes: on Monday April 19, @02:08PM (#31900426)
Obligatory post pointing out that nobody cares what an AC says
Where are my mod points?!?
Re: (Score:3, Funny)
Obligatory post pointing out that funny doesn't give karma.
WebOS does display sanitization by default (Score:5, Interesting)
You have to explicitly enable the "I know what I'm doing, stop protecting me" flag in your app to allow these types of exploits.
http://developer.palm.com/index.php?option=com_content&view=article&id=1756 [palm.com]
Re: (Score:2)
Sanitization has been on by default [google.com] since WebOS 1.1.
It's up to the individual developers to make sure their app is secure -- which it is by default if they don't disable the security features provided by WebOS.
Re: (Score:2)
Sanitization has been on by default [google.com] since WebOS 1.1.
It's up to the individual developers to make sure their app is secure -- which it is by default if they don't disable the security features provided by WebOS.
This suggests that the developer of the SMS app in question (which is still Palm, I think) explicitly declined to utilize WebOS's sanitization support. While I'll give basic kudos to the WebOS developers for foreseeing this issue and negating it by default, it still stands that Palm released a live operating system with a vulnerable (at its own request) SMS application. The WebOS developers might have been smart, but the SMS application developers ruined the party for everyone.
So anyone want to brainstorm w
Re: (Score:1)
That may indeed be true but how many release-quality products do you think ship with that code turned off for performance reasons?
Re: (Score:2)
Re: (Score:3, Insightful)
Sure, the developers should have known better, but issues like this pop up due to an inherent problem in most software development processes. That problem is that specs are written that say what the software should do. Every once in a while the specs note a couple things the software shouldn't do. The specs then go to testers who make sure that the software does everything in the specs and, when it meets spec, everyone signs off. There's often little attention paid to making sure that software DOESN'T d
Re: (Score:2)
This Just in... (Score:2)
Other 'news' - Apparently, Apple is going to make a phone! Maybe it's will be as big as the Ipod!
Re: (Score:2)
Why give them credit? They must have had very shitty standards to allow this bug to exist in the first place, so who's to say there arent more?
Dangerous? (Score:2)
Re: (Score:3, Insightful)
What if you're trying to call 911 but your phone has been rooted? I'd call that dangerous and could very easily cost lives or property...
Re: (Score:3, Insightful)
Re: (Score:1)
Re: (Score:2)
To be pedantic, emergency calls are priority-routed through any available GSM network, and it even works without a SIM card in the phone. Although apparently they want to disable that last feature because too many idiots call up 911 without a card in the phone, and they can't trace them.
Re: (Score:2)
Re: (Score:2)
Yes, they are. I would consider a phone that has longer battery life to be safer.
Re: (Score:2)
How long is long enough for you then? Emergencies generally can't be predicted, so unless your battery life is "infinite", it's just as possible that you'll desperately need your phone 5 minutes after you take it from the charger as it is that you'll need it 12 hours after its last charge....
Re: (Score:2)
I would say at least 48 hours, if I spend the night out I should'nt have to bring a charger. This is becoming less of a problem with the introduction of universal chargers, but most people have proprietary chargers still. An emergency can and has arrived on my way home from a friend's house late one night, my phone was dead - it only lasts about 10 hours.
Re: (Score:2)
this bug and vulnerabilities are bad, even severe, but dangerous? I can think of no scenario where lives or property would be at stake. I guess the personal data could be used for something untoward....
What if they used the dreaded "KaBoom" SMS exploit to trigger the Palm's self destruct mechanism? Then their personal data would be allllll over the place.
Re: (Score:1)
this bug and vulnerabilities are bad, even severe, but dangerous?
Considering the WebOS has only about 5% of the smartphone market [prethinking.com], it's probably not very dangerous at all.
Re: (Score:2)
Re: (Score:2)
Six weeks after the newspaper runs a story accusing you, your employer gives you a pink slip, and the entire town vilifies you....
Re: (Score:2)
Re: (Score:1)
I can think of a few, especially with the medical field. If a hospital can't get in touch with the doctors on call because they all have similarly compromised phones then I'd imagine that patient care would suffer. Or if the phones become so glitchy that Epocrate's drug interaction checker doesn't work, leading to that step geting skipped since there's no time to do it manually (3! to 15! possible interactions per patient). Or the doctor's account on the EMR system is compromised so patient information i
Re: (Score:1)
Of course not, they all carry Blackberries.
Re: (Score:1)
Re: (Score:2)
Re: (Score:1)
Re: (Score:2)
Trust me, most of the time, the nurses don't need you. You just get in the way of people doing actual patient care.
(GF is a nurse, father is a doctor, sadly, this isn't a troll.)
Wow (Score:5, Insightful)
Re: (Score:2)
Re: (Score:2)
It took this long to find.
Hey, this is the fastest exploit ever done by a user community... of about 3 people. ^^
Re: (Score:2)
You are making the assumption that the part that does the rendering of the SMS calls and formatting were part of the same group that takes the SMS and call the function. You assume that this was in the specs for people to follow. And no one brought it up because they though the other team has the problem fixed. And the they had a timeline where they could make this issues for all systems...
Re:Wow (Score:4, Interesting)
Re: (Score:2)
That wasnt actually an exploit.
That was someone forgetting to disable a debugging shell with a global input hook :-p
eh hem... (Score:2)
There are so many wrongs going on at once there. I'll just pick one, load a round in the chamber and mutter 'rudimentary' is redundant. Ok, two...'injection bug'? WTF? --- now get off my lawn!
WebOS 1.4 (Score:5, Interesting)
Re: (Score:1)
Re: (Score:1)
Re:WebOS 1.4 (Score:5, Informative)
1.4 explicitly fixed these issues.
Re: (Score:2)
But a headline of 'Severe bug fixed several revisions back, all is safe' isn't as likely to get readers.
Re: (Score:3, Funny)
Indeed. I actually jumped into the developer's IRC channel to check in on this, and one of them told me about it being fixed already.
I felt like an ass. Thanks, Slashdot.
Anonymous Coward (Score:2, Informative)
This has been fixed with the 1.4 update, not sure why it's news.
Re: (Score:2)
This has been fixed with the 1.4 update, not sure why it's news.
It's news because it was in a 1.x version and it's a basic coding fuckup they were slow and careless not to have fixed before now.
Who knows what else they have yet to fix?
That's why it's news.
Re: (Score:2)
Re: (Score:1)
Re: (Score:1)
Re: (Score:1)
Re: (Score:3, Informative)
Nohing to see here, please move along (Score:3, Informative)
From the source release:
(Note: the findings herein affect WebOS 1.3.5. Palm has since released WebOS 1.4, which fixes these vulnerabilities, though not all handsets or carriers are running this version. Due to contractual agreements, the public disclosure of this information was delayed.)
Javascript Handicap (Score:2)
These bugs can all be traced back to that fact that WebOS is essentially a web browser and the applications are written in JavaScript and HTML.
The article is accurate in so far as JavaScript is concerned. Palm has a long way to go if they ever hope to implement javascript securely on the scale they're using it. Checks have to be built into the SDK and the client engine, and they have to be updated regularly (quite frequently if Firefox' Noscript is any benchmark).
I've authored enough JS (not to be confused with CSS) to doubt that Palm will be able to do it. Nobody else has implemented JS securely, so WebOS device owners should expect to be hack
Minor thing on minor OS in old version has bug (Score:2)
I'm going to get flamed for this but... (Score:2)
This is why "software engineering" fails to be taken seriously. How in this day and age an OS can be released without simple checks and balances like input validation is beyond me. The only excuse is "the developer couldnt be bothered, and no-one checked up on him".
Most programmers these days are the equivalent or tradespeople and artisans - sure many of them are very talented, but as a group still lack the formal QA and inherent attention to risk management that any real engineering should have.
Re: (Score:2)
Sorry, it was the SMS client and not the core OS, but the fact that it could still be hacked though injection is bad.
I don't understand (Score:1)
Obligatory... (Score:1)
FacePALM!
For Extra Credit... (Score:1)