That's the message from researchers at the University of Pennsylvania, who presented a paper at this week's Usenix conference analyzing "Smudge Attacks on Smartphone Touch Screens."
Based on their results, "the practice of entering sensitive information via touchscreens needs careful analysis," said the researchers. "The Android password pattern, in particular, should be strengthened." But they cautioned that any touchscreen device, including ATMs, voting machines, and PIN entry devices in retail stores, could be susceptible to smudge attacks.
Touchscreens, of course, are an increasingly common feature of mobile computing devices. According to Gartner Group, 363 million touchscreen mobile devices will be sold in 2010, an increase of 97% over last year's sales. But are passwords entered via touchscreens secure?
To find out, the researchers studied two different Android smartphones, the HTC G1 and the HTC Nexus1, evaluating different photography techniques for discerning a smudge pattern. With the best setup, they saw a complete smudge pattern two-thirds of the time, and could partially identify one 96% of the time. Furthermore, in ideal conditions -- say, if an attacker had physical possession of the device -- the researchers could oftentimes see finger-stroke directionality too, meaning that "the order of the strokes can be learned, and consequently, the precise patterns can be determined," they said.
While Android 2.2 adds an option for alphanumeric passwords, the team tested the numbers-only password protocol, which uses a virtual nine-digit keypad and imposes certain restrictions on repeat "contact points," as well as swipe patterns. The researchers note that numeric passwords are likely to remain the norm, especially for power users who must continuously "swipe in" to their device.
Given the contact point restrictions, the researchers found that "the password space of the Android password pattern contains 389,112 possible patterns." But an attacker will face a lockout -- typically, 30 seconds in duration -- after inputting an incorrect password. That would make manually entering too many passwords laborious. But by comparing smudge patterns with a dictionary of common patterns, an attacker might significantly reduce the password space. Thankfully, there's a failsafe on Android phones, since after 20 failed password attempts, a user must enter his or her Google username and password to authenticate.
The good news is that for now, even with a smudge attack, an attacker typically wouldn't be able to reduce the password space to 20 or fewer possibilities. But going forward, don't rule out the possibility that enterprising attackers may add on additional techniques to help see through smudges.
Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.