Google Wallet locked after flaw found

The tech giant disables prepaid card use on its Wallets after a researcher finds a security hole.

Mobile wallets

Google has disabled the use of prepaid cards in its Wallet service after security researchers claimed a flaw in the technology could allow a hacker to acquire the user's PIN number.

The company temporarily disabled provisioning of prepaid cards for Google Wallet as a precaution until a permanent fix was found.

Despite the action and the research that inspired it, Google claimed its Wallet was perfectly safe to use. It said security issues were more likely to arise if users rooted their phones.

We were able to uncover the contents of the binary data and were shocked at what we found.

Advertisement
Advertisement - Article continues below
Advertisement - Article continues below

"People are asking if Google Wallet is safe enough for mobile phone payments. The simple answer to this question is yes. In fact, Google Wallet offers advantages over the plastic cards and folded wallets in use today," said Osama Bedier, vice president of Google Wallet and Payments, in a blog post.

"But sometimes users choose to disable important security mechanisms in order to gain system-level root' access to their phone; we strongly discourage doing so if you plan to use Google Wallet because the product is not supported on rooted phones. That's why in most cases, rooting your phone will cause your Google Wallet data to be automatically wiped from the device."

The flaw itself did require root privileges to succeed.

Finding the flaw

Joshua Rubin, a senior engineer with zvelo, claimed to have found the vulnerability in Wallet after looking through a "metadata" table in the database used by Google Wallet.

After cracking open the "deviceInfo" row within that table, he uncovered plenty of valuable information.

Advertisement - Article continues below

"We were able to uncover the contents of the binary data and were shocked at what we found," he explained in a blog post.

"Unique User IDs (UUID), Google (GAIA) account information, Cloud to Device Messaging (C2DM, also known as "push notification") account information, Google Wallet Setup status, "TSA" (this is probably related to "Trusted Services" not the "Transportation Security Administration") status, SE status and most notably "Card Production Lifecycle" (CPLC) data and PIN information."

Subsequently, Rubin discovered in the PIN information section a long integer "salt" and a SHA256 hex encoded string "hash." All he had to do then was run a brute force attack to determine the PIN itself.

"It dawned on us that a brute-force attack would only require calculating, at most, 10,000 SHA256 hashes. This is trivial even on a platform as limited as a smartphone. Proving this hypothesis took little time," he added.

Advertisement
Advertisement - Article continues below

"Google Wallet allows only five invalid PIN entry attempts before locking the user out. With this attack, the PIN can be revealed without even a single invalid attempt. This completely negates all of the security of this mobile phone payment system."

Rubin said he had been in contact with Google and the company said it was working quickly to resolve the issue.

Advertisement - Article continues below

The researcher suggested Google may have some trouble in releasing a proper fix as it needed to move the PIN hash and salt details into the Wallet's Secure Element (SE), used to store and encrypt sensitive data like credit card information. This would take time and mean additional financial costs for banks allowing customers to use the service.

"At present, the decision is in the banks' hands. They may actually choose to accept the risk imposed by this vulnerability rather than incur the financial and administrative overhead of allowing Google to release a proper fix (and thereby potentially put the banks on the hook for the PIN security)," Rubin added.

"zvelo feels that this would be a grave mistake and would expose users to undue risk."

It appears Google has been given time to resolve the issue.

Featured Resources

What you need to know about migrating to SAP S/4HANA

Factors to assess how and when to begin migration

Download now

Your enterprise cloud solutions guide

Infrastructure designed to meet your company's IT needs for next-generation cloud applications

Download now

Testing for compliance just became easier

How you can use technology to ensure compliance in your organisation

Download now

Best practices for implementing security awareness training

How to develop a security awareness programme that will actually change behaviour

Download now
Advertisement

Recommended

Visit/malware/33080/hackers-abuse-linkedin-dms-to-plant-malware
malware

Hackers abuse LinkedIn DMs to plant malware

25 Feb 2019
Visit/cloud/cloud-computing/354479/google-adds-partners-to-real-time-translation-tools
cloud computing

Google adds partners to real-time translation tools

8 Jan 2020
Visit/hardware/354336/the-it-pro-products-of-the-year-2019-all-the-years-best-hardware
Hardware

The IT Pro Products of the Year 2019: All the year’s best hardware

24 Dec 2019
Visit/security/malware/28083/the-five-best-free-malware-removal-tools
Security

Best free malware removal tools 2019

23 Dec 2019

Most Popular

Visit/policy-legislation/data-governance/354496/brexit-security-talks-under-threat-after-uk-accused-of
data governance

Brexit security talks under threat after UK accused of illegally copying Schengen data

10 Jan 2020
Visit/security/cyber-security/354468/if-not-passwords-then-what
cyber security

If not passwords then what?

8 Jan 2020
Visit/policy-legislation/31772/gdpr-and-brexit-how-will-one-affect-the-other
Policy & legislation

GDPR and Brexit: How will one affect the other?

9 Jan 2020
Visit/web-browser/30394/what-is-http-error-503-and-how-do-you-fix-it
web browser

What is HTTP error 503 and how do you fix it?

7 Jan 2020