Quantcast StorefrontBacktalk » Blog Archive » Check-In Services Glitches Allow Customer Impersonation
advertisement
advertisement

Check-In Services Glitches Allow Customer Impersonation

Written by Evan Schuman
June 17th, 2010
Like this story? Share it
To share this story with people in your social network, please click on the network icons below.

The increasingly popular check-in services, where users let friends know where they are by “checking in” at specific retailers using their smartphones, have two major security flaws, according to one independent testing firm.

The first allows consumers to easily impersonate other users—and thereby access their rewards, which means the stores are not attracting the consumer they wanted to attract—and the second defeats users’ efforts to go into a confidential mode, where their whereabouts are not supposed to be distributed.

At least one of the check-in services, which include Foursquare, Gowalla and Brightkite, suffers from the impersonation bug, according to Matt Johnston, VP/Marketing for uTest, a crowd-sourced software testing firm. Johnston wouldn’t say which vendor’s products suffer from that flaw.

The impersonation bug involves changing a few characters in the URL. Specifically, the consumer replaces his/her login name with the name of the person being targeted. Getting users’ names is easy, especially if you’re already on one of their lists.

With that URL change—no password is required—the system allows all E-mail and privacy settings to be changed, which should provide access to all data.

The problem with the end-user privacy setting—termed something like “going dark,” “offline” or “off the grid”—is that, according to one uTest reviewer, “if anyone subscribes to this feed via RSS, they continue to see your off-the-grid checkins. So my secret date or job interview is no longer private!”

The vendor with that last glitch, Johnston said, had apparently tried to be thorough in its off-the-grid feature, “as it did shutdown synching with Facebook and Twitter. They considered this, but they didn’t take it all the way through.”

Johnston said the companies with the glitches had been alerted and are in the process of trying to address the problems.


advertisement

Leave a Reply

Newsletter

Quickly catch-up on the latest in E-Commerce and Retail Tech with our free weekly newsletter, with urgent bulletins as news merits.
advertisement

Most Recent Comments

Kill All The Passwords

This article does mention, but does not give enough attention to, the fact that the attacks discussed are only feasible when the encrypted password file can be copied and subjected to an offline attack. The trick is to have authentication performed on a separate, much more strongly secured host - such as an Active Directory Domain Controller, or a Kerberos server, or a NIS+ server, or even using something as banal as an LDAP-over-SSL authentication dialog. In these environments, the odds of the "password file" being stolen and subjected to an offline attack go to near zero, and only online attacks may be carried out by the attacker. With sensible exponential backoff between failed password attempts, lockout after a modest number of failed attempts on a single account, and pattern detection, that minimum 7 character password is quite secure enough. Passwords aren't dead yet for security purposes, and they will be with us for a very long while to come for practical purposes. The trick is to employ them correctly. Read more...
The possibilities you describe are years away from being implemented at best, so for the moment passwords are an ugly reality. Luckily, password managers can easily manage hundreds of passwords of any length. The only thing a user needs to remember is the master password. It seems like an easier task to educate users on how to use password managers rather than implement complex security technology on a global basis. Read more...