Vulnerabilities / Threats

8/11/2010
12:00 PM
50%
50%

New Mobile Security Threat: Fingerprint Oil

Oily residue left on touchscreen mobile devices may help an attacker deduce password

Prepare for a new mobile security threat: smudges. Or to be more precise, the oily residue left behind by fingers on your iPhone, Android, BlackBerry, or other touchscreen mobile device may help an attacker deduce your password.

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.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Devastating Cyberattack on Email Provider Destroys 18 Years of Data
Jai Vijayan, Freelance writer,  2/12/2019
Up to 100,000 Reported Affected in Landmark White Data Breach
Kelly Sheridan, Staff Editor, Dark Reading,  2/12/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-8354
PUBLISHED: 2019-02-15
An issue was discovered in SoX 14.4.2. lsx_make_lpf in effect_i_dsp.c has an integer overflow on the result of multiplication fed into malloc. When the buffer is allocated, it is smaller than expected, leading to a heap-based buffer overflow.
CVE-2019-8355
PUBLISHED: 2019-02-15
An issue was discovered in SoX 14.4.2. In xmalloc.h, there is an integer overflow on the result of multiplication fed into the lsx_valloc macro that wraps malloc. When the buffer is allocated, it is smaller than expected, leading to a heap-based buffer overflow in channels_start in remix.c.
CVE-2019-8356
PUBLISHED: 2019-02-15
An issue was discovered in SoX 14.4.2. One of the arguments to bitrv2 in fft4g.c is not guarded, such that it can lead to write access outside of the statically declared array, aka a stack-based buffer overflow.
CVE-2019-8357
PUBLISHED: 2019-02-15
An issue was discovered in SoX 14.4.2. lsx_make_lpf in effect_i_dsp.c allows a NULL pointer dereference.
CVE-2013-2516
PUBLISHED: 2019-02-15
Vulnerability in FileUtils v0.7, Ruby Gem Fileutils <= v0.7 Command Injection vulnerability in user supplied url variable that is passed to the shell.