PCMag editors select and review products independently. If you buy through affiliate links, we may earn commissions, which help support our testing.

Google Wallet Woes Continue

 & Neil J. Rubenking Principal Writer, Security

Our team tests, rates, and reviews more than 1,500 products each year to help you make better buying decisions and get more from technology.

Our Expert
LOOK INSIDE PC LABS HOW WE TEST
65 EXPERTS
43 YEARS
41,500+ REVIEWS

275
Yesterday we reported a vulnerability in Google Wallet. If the product is installed on a rooted Android phone, a quick, simple brute force attack can extract the PIN and allow a thief to spend your Google Wallet funds. The simple solution—don't root your phone. Comments around the Web suggested that won't help because the thief could root the phone ex post facto. Fortunately, that's not the case. Unfortunately, today brings more bad news.

Google's Response

A Google spokesperson quickly responded to my post about the PIN vulnerability yesterday, saying "The zvelo study was conducted on their own phone on which they disabled the security mechanisms that protect Google Wallet by rooting the device. To date, there is no known vulnerability that enables someone to take a consumer phone and gain root access while preserving any Wallet information such as the PIN. We strongly encourage people to not install Google Wallet on rooted devices and to always set up a screen lock as an additional layer of security for their phone."

I double-checked with Google and was told that rooting an Android phone will wipe all data. That statement struck me as odd, because there are a number of well-known ways to root an Android phone without wiping its data. For example, unrevoked.com automatically roots most EVO phones, and the Super One Click utility will root a wide variety of phone types.

I checked back with Google; they remained adamant that rooting a phone wipes its data, period, and asked me to forward any evidence to the contrary. Eventually we sorted out a communication problem. As Russell Holly, ExtremeTech's top Android expert, verified, many Android phones can be rooted without wiping their data, but no device that supports Google Wallet can be treated this way. Rooting a Nexus S 4G will definitely wipe its data.

That being the case, if you refrain from rooting your phone you're protected against the PIN vulnerability. You should still go ahead and take the additional security steps recommended by the researcher who discovered the problem: enable a screen lock, disable USB debugging, enable full disk encryption, and keep your device fully up to date.

A Second, Worse Vulnerability

Google's problems didn't end there, however. A site titled The Smartphone Champ revealed a second flaw, one that works on any phone rooted or not.

Simply put, a thief can gain access to all funds in your Google prepaid card by wiping out Google Wallet's data and launching it again. On launching without any data, Google Wallet invites the thief to connect with a Google account and create a new PIN. But since the prepaid card is linked to the device, not the account, all the thief needs to do is select the default card for instant access to your funds. A video on the Smartphone Champ site walks through the simple steps required.

Google has verified this vulnerability. A spokesman stated, "We strongly encourage anyone who loses or wants to sell or give away their phone to call Google Wallet support toll-free at 855-492-5538 to disable the prepaid card. We are currently working on an automated fix as well that will be available soon. We also advise all Wallet users to set up a screen lock as an additional layer of protection for their phone." (Actually, no matter what sort of mobile device you use setting some kind of screen lock is a must.)

The Google representative I spoke with this morning confirmed that a fix will be released as soon as possible, probably within a few hours. If you're one of the lucky few whose carrier and hardware support Google Wallet, you'll want to keep your phone extra safe and watch closely for that fix.

About Our Expert

Neil J. Rubenking

Neil J. Rubenking

Principal Writer, Security

My Experience

When the IBM PC was new, I served as the president of the San Francisco PC User Group for three years. That’s how I met PCMag’s editorial team, who brought me on board in 1986. In the years since that fateful meeting, I’ve become PCMag’s expert on security, privacy, and identity protection, putting antivirus tools, security suites, and all kinds of security software through their paces.

Before my current security gig, I supplied PCMag readers with tips and solutions on using popular applications, operating systems, and programming languages in my "User to User" and "Ask Neil" columns, which began in 1990 and ran for almost 20 years. Along the way, I wrote more than 40 utility articles, as well as Delphi Programming for Dummies and six other books covering DOS, Windows, and programming. I also reviewed thousands of products of all kinds, ranging from early Sierra Online adventure games to AOL’s precursor Q-Link.

In the early 2000s, I turned my focus to security and the growing antivirus industry. After years of working with antivirus, I’m known throughout the security industry as an expert on evaluating antivirus tools. I serve as an advisory board member for the Anti-Malware Testing Standards Organization (AMTSO), an international nonprofit group dedicated to coordinating and improving testing of anti-malware solutions.

The Technology I Use

Much of the testing I do, particularly testing with real-world ransomware, is just plain dangerous. To perform such tests safely, I sequester them inside virtual machines managed by VMWare Workstation. For cross-platform testing, I use a MacBook Air, a Google Pixel 4, and a 6th-generation iPad.

I rely on my Delphi coding skills to create and maintain small applications. These include programs to check whether an antivirus correctly handled the malware it detected, launch dangerous URLs and record the security program’s reaction, and analyze the malware that I collect for use in testing. I also wrote a tiny browser and text editor for use in testing security apps that have predefined reactions for known products.

I do my writing and research on a Dell OptiPlex desktop, relying on Microsoft Word (my fingers know all the shortcuts). Many of my articles include charts and analysis; Excel is my go-to for those. When work hours end, though, I escape the bounds of Microsoft and Windows. There’s an iPhone in my pocket, I relax with my oversized iPad, and my Kindle Oasis is always loaded with the best science fiction and fantasy.

Read full bio