Google Wallet PIN Cracked

Fix for mobile payment vulnerability could require banks to take over some security responsibility.

When researchers late last year revealed that the Google Wallet app stored sensitive user data in plain text locally on the device, they also gave the app credit for its PIN protection. But now that last line of defense has been exposed by another researcher, who this week released a proof-of-concept (PoC) for cracking the Google Wallet PIN.

Joshua Rubin, senior engineer with Zvelo, posted his PoC that demonstrates how he cracked Google Wallet's four-digit PIN, used to authorize and process mobile-phone payments. The PIN is considered the extra layer of security that a plain, old credit card wouldn't have. But Rubin poked a big hole in that strategy: "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 in a blog post.


More Security Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

In December, researchers at viaForensics said they had found that the app locally stores some payment card data in plain text, such as the cardholder's name, transaction dates, email address, and account balance.

Google Wallet lets consumers transact credit-card charges, redeem gift cards, and use loyalty membership cards in stores from their phones. To run the app, the users must type in their four-digit PINs when they launch the app.

While Google Wallet hides the full credit-card account number, the last four digits reside in plain text in the app's local SQLite database, viaForensics found. viaForensics also found that the app repels man-in-the-middle attacks, and at the time gave the app credit for being protected by a PIN to conduct transactions with the cards.

Zvelo's Rubin, who posted details on the PoC as well as a video of it, was able to brute-force the PIN, which was a long-integer "salt" plus a SHA256 hash.

Wallet uses near field communication (NFC), based on RFID technology, and it communicates with a so-called secure element (SE) stored in a chip on the device. "It's like the chip and pin model in European credit cards," says Tyler Shields, a security researcher with Veracode.

Read the rest of this article on Dark Reading.

It's no longer a matter of if you get hacked, but when. In this special retrospective of news coverage, Monitoring Tools And Logs Make All The Difference, Dark Reading takes a look at ways to measure your security posture and the challenges that lie ahead with the emerging threat landscape. (Free registration required.)


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS

Resource Links