Holding your phone wrong is … right?

A big joke in the cellphone industry was the excuse Apple gave for the “antennagate” issue upon introduction of the iPhone 4: “you’re holding it wrong.”  Funny enough, holding it wrong may be the way to go in the future.

You’ve probably seen published lists of the most commonly used PIN numbers, including such creative numerology as 1111 or 5683 (spells out LOVE). Security experts look at those lists and shake our heads wondering what people were thinking when they hit “1” four times and thought their phone was secure.

Of course, at least they’re using a PIN of some sort in an effort to protect their phone. Even if the PIN is considered “weak,” the stark reality is most people don’t use one simply because PIN codes are inconvenient and take time to enter. In fact, most people don’t use any means of data protection at all.

Thank goodness you’re not one of those PIN-less cellphone users, right?

Well, what if I told you your PIN, no matter how cleverly created, is now trivial to hack?  And that nifty complicated thumb sliding lock pattern you came up with that would require the hacker to be double-jointed to pull off?  Even easier.

There’s a new PIN and lock pattern proof-of-concept hack from Dr. Adam Aviv and his team of researchers at the University of Pennsylvania that uses the accelerometer in your phone to detect how it moves in space specifically during the unlock process.  As you move your thumb to hit the PIN numbers or trace the unlock pattern, this hack track the accelerometer data and matches it against its database of known patterns. They’ve been working on this attack vector for a few years now. Their previous approach utilized the gyroscopic sensors which lead to very imprecise measurements, but this new approach uses the accelerometer sensor in a “high bandwidth” mode and the results are pretty spectacular. In controlled settings with the subject seated they were able to guess the PIN number used 43% of the time and the unlock pattern 73% of the time.  When the subject was walking, the accuracy dropped greatly due to the additional movement noise introduced to the sensors that resulted in only 20% of PINs and 40% of patterns guessed.  They also mention the possibility of utilizing machine learning to determine text-based passwords as well, but mention no collected data against it.

I suspect long key presses for alternate characters may be difficult to decipher from the accelerometer data, but they do briefly mention key permutations (each key having multiple values from long presses), which increases the number of guesses required to get a four number PIN combination. If one were to use a very complicated password or random characters you could make it highly unlikely to guess your password using this method. Of course, you would also be spending the bulk of your time on your Smartphone entering an unlock password.

Another possible solution is to change the orientation of your phone (i.e. holding it wrong). Since Dr. Aviv’s team is only reading the accelerometer values and not the gyroscope values, which track pitch and roll of your phone, one could throw their data off. If they accounted for this circumstance and polled the gyroscope to determine orientation values while polling the accelerometer, the data sets would be much more complex as a result.

So clearly the best response to this type of attack method is to boogie down, run, jump, etc. while unlocking your phone. Personally, I’m working on some sick dubstep and James Brown moves to go along with my android unlock pattern that should make it near unreadable.

 

In the News

Here are three security articles we found rather interesting this week.

Researcher Wows Black Hat with NFC-based Smartphone Hacking Demo (CIO)

Accuvant Labs researcher Charlie Miller has figured out how to break into the Google/Samsung Nexus S and the Nokia 9 smartphones by using Near Field Communication (NFC).

I can read all the files, said Miller about how he managed to break into the Nokia 9 when his home-made NFC-based device is in very close proximity to the targeted smartphone. I can make phone calls, too. Vulnerabilities he identified in the Android-powered Nexus S were located in the browser surface, he said.


The truth behind those Nigerian 419 scammers
 (TechRepublic)

419 Advanced Fee Fraud (also known as the Nigerian 419 scam) is still being used quite frequently to steal money from gullible victims via fraudulent emails. But are these emails really coming from Nigeria, or are they perpetrated by attackers from other countries?

Researchers from the University of Ibadan found the following IP locations within 400 scam emails tested:

The Wisconsin Department of Revenue: A Bargain for the Identity Theft Collective (The Huffington Post)

Adam Levin of Credit.com wrote an interesting story documenting Wisconsin’s complete inability to secure public information.

Last week, the Wisconsin Department of Revenue revealed that it had accidentally made public 110,795 Social Security numbers and tax ID numbers of Wisconsin residents. The numbers were mistakenly embedded in a real estate report and posted to the department’s website for almost three months before being removed.

This is the fourth time since 2006 that Wisconsin state agencies have been involved in the public release of Social Security numbers.

 

May Updates and Patch Report: Part 2

It’s interesting how you can go through an entire week of work and think that nothing significant happened in the security world. Now that I am trying to write these updates on a weekly basis, I’m paying a bit closer attention. While we won’t have huge patch-focused updates unless it’s the same week as a patch release, it doesn’t mean nothing has been going on. So, without further ado here are this week’s updates and patch report. If you missed last week’s, read it here.

 

Microsoft

EMET 3.0 has been released. What is EMET you ask?

EMET stands for “Enhanced Mitigation Experience Toolkit” and is basically a tool that allows you to protect Windows applications from attack. We’re used to applying patches for things like this, but sometimes a problem is more complex than people think and patches are a long time coming. EMET allows you to shift from a reactive to a proactive stance. This is a different way of protecting your systems and will take some work to get started. However, if your operational guidelines have matured to the point you have identified allowed applications and are either using application control or imaging, this can provide a nice additional layer of protection. With this new version, you can also identify attempts to exploit vulnerabilities, which can give you preliminary warnings of attack.

 

Google

Google has released a new version of Chrome. This new version adds a few features and patches several security bugs. If you are running Chrome, it should have automatically updated. If you want to verify the update has gone through, go to Tools->About and make sure you’re running version 19 or higher.

 

Apple

Apple has released a new version of QuickTime. This version patches seventeen problems and affects the application on both Windows and OSX. If you use it, patch it.  Details are here.

 

Android

Trail of Bits published an interesting article on the relative security merits of Android versus iOS. The heart of their argument is Android phones aren’t updated as often as the iPhone and the Android marketplace is more flexible and this brings additional malware risk.

While this is true, it is also true the reduction of controls allows for faster development. Additionally, the deployment of Android updates is the job of the carrier, not of Google. Blaming Google for the carriers’ unwillingness to deploy updates to older phones is, I think, unfair. The real problem is carriers make more money when people buy new phones, so the longer they support the old phones, the less money they make. Apple has embraced this economic reality by convincing people to throw away their devices and buy new ones every year or so.

So here’s the truth.  If you are concerned about malware you have three options:

1) Use iOS and trust Apple to protect you. Do not jailbreak anything and live with what you get.

2) Use Android and run an anti-malware agent. I like Sophos Mobile Security (beta) and Lookout. On my phone, at least, they even seem to play well together. Don’t install apps willy-nilly.

3) Use Android, run an anti-malware agent (as above), root it and install firewall and adblockers. This makes you more vulnerable to malware, but gives you additional protection to (somewhat) make up for it. Optionally install your own ROM.

You do have to be more vigilant, but if that’s not a problem for you, you can actually get a more secure device than you can with IOS, as you are in charge of your updates and you don’t have to wait for it to fit within a company’s lifecycle.

 

sudo

A very interesting bug in sudo was discovered. There’s no point in my describing it here, as they did such a good job on Sophos Naked Security. Definitely go there and read about it.

 

RealPlayer

RealPlayer has a brand new update. It patches three vulnerabilities in different levels of the product. However, the fourth vulnerability “why are people still using RealPlayer?” remains unpatched. :)

Apply the fix or remove the software.  The latter is generally a better choice.

 

HULK

A new denial of service tool is out. Known as the HTTP Unbearable Load King or “HULK,” it is different in that it takes greater care to make sure requests are unique. With a traditional DDoS tool, you can often find a traffic pattern to filter out and mitigate the attack. However, the more different each request is from one another, the harder this is to do. This tool raises the bar for DDoS protection.

If you are running a DDoS protection tool, take a look at the tool and check it against your protection system.  If it bypasses it, complain to your vendor so they fix the problem.

If you are not running a DDoS protection tool and are comfortable accepting the DDoS risk, just sit back and chuckle over the fact the most stealthy DDoS tool is known as The HULK.

 

That’s it for this week.  If you have any questions, please drop us a note.

Is this the end of carrier bloat as we know it?

Carrier bloat … if you have a Smartphone, you probably know exactly what I’m talking about. Carrier bloat usually takes the form of targeted mobile marketing applications that encompass everything from sports and shopping, to games and movies. The apps are baked into the phone’s software,  often run by default, can’t be removed and worst of all, gobble up precious storage space, CPU cycles and battery life. Simply put, carrier bloat holds your phone hostage.

I’m a big fan of rooting Smartphones by loading a custom ROM that strips away all the non-essential garbage the carriers preload onto each device. It’s amazing how much longer your battery will run, as well as how much more talk and text time you will have, when the added overhead of carrier bloat is removed. Why does it suck up so many resources? The bloatware is constantly dialing home to check on updates and frequently reports back to the carrier regarding what you’re up to (*cough* CIQ  *cough*). I guess I’m just one of those old school guys that believes when you purchase a device, you own the hardware and have total control over what is running on the device. What a novel concept!

If I don’t like the underwater basket weaving app included with the phone, I shouldn’t have to put up with Sprint, T-Mobile, or AT&T’s version of that app for the life of the product. I paid several hundred dollars for the hardware and I have a say in what the phone is or isn’t running. I didn’t pay the carrier to spy on my activities or offer me products and services that I don’t care for or use. I’m paying these clowns to provide me with voice and data service … that’s it. And when I root a device and strip it bare, I’m getting exactly what I want and technically what everyone thinks they’re paying for.

Not surprisingly, I’m not alone in this line of reasoning. XDA Developers has at this time a little over 4.4 million members. The site specifically caters to custom ROM development for pretty much every Smartphone you can buy today. Developers on this site figure out how to root the devices and then customize the software loaded onto each device. The real kicker here is the carriers and mobile device manufacturers watch this site very closely as it is often XDA who manages to load new versions of Android on older phones and extend the usefulness and security of said phone before the carrier gives up on it entirely.

Take the HTC Evo 4G for example. HTC had stated they weren’t sure if the device was capable of running Gingerbread. It wasn’t until someone on XDA had successfully ported it over from a ROM on a newer HTC phone that HTC announced a few months later that it was releasing an official update that would upgrade the Evo 4G to Gingerbread.

Luckily, the times be changing!

Google started a little pilot project last month involving Google Wallet and a completely unlocked carrier-independent Samsung Galaxy Nexus smartphone. The phone has no carrier bloat and no carrier contract. It’s simply a pay as you go GSM device that works on any GSM network (AT&T and T-Mobile here in the US). You pay for your minutes through Google wallet and Google reimburses the carrier for your used bandwidth. It’s being described as “Android in pure unadulterated goodness.”

For light phone users this is a perfect phone. You essentially pay for only the time you spend on data and voice usage with no carrier bloat eating away at your data minutes … it only uses what you tell it to use.  For guys like me that are heavy data users and who rely on unlimited data access plans (I spend a lot of time on customer sites using my phone for network access), this will be a very expensive device. It’s not quite there yet for us, but it’s a good step in the right direction for many other users.

The goal of this project is to take control of the device out of the hands of the carrier who ideally should only be involved in providing voice and data services and not dictating to the customer what they can or cannot run on said device. And it’s not like this is the first time a communications provider has taken advantage of its power.

This was a particularly sore point I had with Comcast cable service. They would outright block Netflix at times or downgrade the network traffic to the popular streaming website to the point their product was unusable. Comcast isn’t happy that Netflix is giving Comcast customers options. They want to maintain a closed market environment and don’t like competition for their OnDemand product offering. Like many other consumers, as soon as DSL was available in my area I kicked Comcast to the curb. I voted with my wallet and went with a more open carrier.

Sadly there are those out there that live in locations where Comcast is the only option and they are therefore stuck with a monopolizing provider. Up until Google started their exciting new project, a large percentage of smartphone owners were at the mercy of their carriers for what exactly is installed and running on their phones until Google started their exciting new Smartphone project.

If you’re a Smartphone user who is tired of a carrier who manipulates your phone, it’s time for you to vote with your wallet as well and switch to a phone that doesn’t hold you hostage.

In the Chicago area? Visit us at ForenSecure.

RJS Smart Security will be at ForenSecure in Wheaton, Illinois this Thursday and Friday (19th and 20th). To quote ForenSecure’s website, “This multi-track, technical conference attracts 200+ professionals for an intensive one-and-a-half day schedule that includes discussion and debate over forensics, security, data/information governance, cyber crime and security, ethical hacking, eDiscovery, cloud forensics, steganography, policy and compliance, privacy, wireless security, cloud computing, and identity theft.”

ForenSecure'12

At 10:50am on Thursday, our very own Adam Johnson will be presenting Mobile Devices: Security Through Monitoring and Control. If you’re interested in learning about the current landscape of the mobile industry and the relatively misunderstood security risks associated with this new technology, this is the perfect session for you. Adam brings a wealth of information to this topic based upon his many years in the mobile industry prior to joining RJS.

If you aren’t in the Chicago area, but are still interested in Adam’s mobile device security presentation, shoot us an email and we’ll send you the slides.

Register for ForenSecure.