Your iPhone’s Achilles Heel
Security Flaw Found in Popular Apple Gadget
 |
Just when you thought it was
safe to receive a text message on your iPhone. Picture
Source |
Do you carry an iPhone? If so, your phone is at risk of being
cyber-jacked. That’s right, the hackers made their way
to your precious iPhone platform.
For decades now, hackers have had the time of the lives systematically
exploiting all the vulnerabilities of the Windows platform;
and just like a comedian depends on a good political buffoon
(we sure have had our share lately), hackers can surely depend
on Windows to keep producing garbage operating systems for
them to tunnel their way into.
But much to my disappointment, it seems like Apple is starting
down the road well traveled, enticed and seduced by the sweet
allure of producing parasitic software at the expense of—you,
the loyal Apple consumer. The guiles of the Micro-serpent
have weighed heavy on the mistress, and she has at last—bitten
the Apple (I just couldn’t resist).
According to the
San Francisco Chronicle, your iPhone can now be attacked
through text messaging. In the April
2009 issue of Flawless Compliance, I wrote about cyber-hackers
cracking the code on the US government’s network of
computers. I mention in the article that they’re able
to pull this off because hackers are very brilliant and largely
underestimated. I wasn’t kidding.
Security experts Charlie Miller and Collin Mulliner are two
such people. They’ve discovered that if somebody sends
the right series of text messages to your iPhone, they can
take over the features of your phone including the web browser,
microphone, and even your camera!
How is this possible? Apparently, there is vulnerability
in the iPhone’s operating system that allows program
code (i.e. executables) to make their way into memory by way
of a simple text message. Come on Apple, are you serious?
Have you not yet heard of email viruses that use the same
ammo (or M.O. if you prefer)?
According to Miller and Mulliner, the messages seem innocuous:
just a bunch of funny squares. This would appear to be the
Generation Y equivalent of the Baby Boomers’ “wrong
number.” But these messages are anything but safe. If
allowed to continue they will eventually embed a potentially
dangerous program in your iPhone’s memory, like a clever
alien in a good science fiction movie. After that the iPhone
is no longer completely under your control.
The good news is that it is easily detectable. The hacker
would need to send hundreds of these messages (512 to be exact)
to be successful, and simply deleting any one of them would
stop the hack. Better yet, the going advice is if you see
any messages with funny squares, just turn off your phone.
Here’s the most alarming part for me which comes straight
from The Chronicle:
“[Miller and Mulliner] said they informed
Apple of the problem a month ago but the problem has not
been patched, according to Forbes, which said Apple has
declined to comment on the issue.”
Oh boy. I would decline to comment too. Boys and girls, this
is where disappointment turns to irresponsibility.
As I mentioned, the disappointment comes from Apple putting
out garbage software. Of course I don’t know the details
of how the iPhone operating system works, but for me this
is over-engineering a solution to a flaw. Meaning, the vulnerability
was probably engineered into the iPhone, not on purpose, but
because they refused to keep it simple. Binary code is unreadable
to humans, so why allow it in a text messaging client? You
have to guard for this on your compliance programs as well.
Don’t over-engineer the solution once your compliance
targets are met, as you may end up actually compromising your
system instead of improving it.
Second, if you find vulnerability fix it. And if somebody
else finds that vulnerability for you, fix it fast! Not fixing
a known compliance violation is the worst kind of trouble
you can get yourself into. Regardless of the situation, it’s
interpreted by auditors as disregard, and these kinds of penalties
only come in the sizes of huge, enormous, and bankrupt.
So please heed my advice on this one: (1) Know what compliant
looks like and when you reach it—stop, (2) Make vulnerability
remediation your number one priority and act fast, (3) St‚y
aw‚y ‚‚from fun‚y iPh‚ne text
‚mes‚‚ges! |