Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats

12/5/2014
04:42 PM
50%
50%

IBM Reveals 'SpoofedMe' Attack Leveraging Social Login Vulnerability

IBM researchers uncovered an attack that takes advantage of the social login feature.

IBM researchers uncovered an attack that could allow a hacker to impersonate someone by abusing the social login mechanism.

Social login is a form of single sign-on that uses existing login information from a social network, such as Facebook or Google+, to sign into a third-party website. According to IBM's X-Force Application Security Research Team, the attack -- which they have dubbed "SpoofedMe" -- works this way: A cyber criminal registers a spoofed account within a vulnerable identity provider using the victim's email address. Then, without having to actually confirm ownership of the email address, the attacker will log into the relying website with the fake account, via social login. The relying website will check the user details asserted by the identity provider and log the attacker into the victim's account, based on the victim's email address value, Or Peles, a security researcher with X-Force, explains in a blog post.

IBM found the issue impacted identity providers Amazon, LinkedIn, and MYDIGIPASS, all of which have taken steps to fix the problem. In one case, IBM discovered the issue could have allowed an attacker to intrude into a Slashdot.org user account using the "Sign In With LinkedIn" service. Once logged in, an attacker would have had total access to the victim's account. LinkedIn responded to the issue quickly and fixed the vulnerability after the attack was disclosed, Peles wrote.  

The attack relies on a combination of two things: a vulnerable identity provider and one of two design problems in the relying website.

"A common relying website design problem is the use of an email address as a sufficiently unique identifier for its local user accounts without verifying the specific identity provider(s) previously used with the account," Peles blogs. "This means that claiming (using an identity provider) to own an email address is enough to log a user in to the local account that uses the same email address. This design problem may arise in cases where support for social login providers was added to an existing system without redesigning the user database in the migration process."

The other design issue for relying sites is account linking, which lets users log into their local account more than one way.  

"When, for the first time, a user logs in with a different identity provider (than previously used with his or her existing local account) and uses an email address that is identical to that of his or her existing account, a website could assume he or she is the owner of the account and automatically link the new identity with the existing local account without asking for any additional credentials," Peles explains.

When it comes to identity providers, IBM found that some agree to supply the account email addresses as part of the social login authentication process even when the user's ownership of the email address has not been positively verified.

In order for the attack to work, the third-party website must support social login with a vulnerable identity provider and request the email address field as part of the social login authentication process. In addition, the third-party site must support at least one other login option either using another identity provider or the ability to use a local website account's credentials. There also must be a victim account whose email address is known and that doesn’t own an identity account with this email address at the vulnerable identity provider.

Diana Kelley, executive security advisor for IBM Systems, tells Dark Reading that there could be thousands of websites vulnerable to this attack. In addition to identity providers Sign-In with LinkedIn, Login with Amazon, and MYDIGIPASS.COM Secure Login, the following relying websites were found to be affected by the issue: Spiceworks.com, Crowdfunder.com, Slashdot.org, Nasdaq.com, Scoop.it, and Idealist.org.

"This is fairly simple to exploit if both the relying website (e.g. NASDAQ/Slashdot) and the identity provider (e.g. LinkedIn before the fix) are vulnerable," she explains in an email. "To exploit it requires registering for an account with an email address that is in use at the relying site but not in use at the ID provider and then using the social login function to login at the relying site."

According to IBM, the implications are serious, as it could be used for a number of malicious activities, including impersonating company executives in a stock forum or other public website with the goal of affecting stock prices. It could also be used to leverage someone's reputation to spread malicious links or malware, or defame them by posting controversial material.

"While fixing the identity provider vulnerability would be enough for this attack to be blocked … it is important for websites that are vulnerable to fix the website design problem because it may expose their users to similar attacks," Peles adds. 

Brian Prince is a freelance writer for a number of IT security-focused publications. Prior to becoming a freelance reporter, he worked at eWEEK for five years covering not only security, but also a variety of other subjects in the tech industry. Before that, he worked as a ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
sunilmadhu
50%
50%
sunilmadhu,
User Rank: Apprentice
12/5/2014 | 5:24:33 PM
IBM should check out Socure's Social Biometrics solution which defends enterprises against this scenario
Socure's Social Biometrics(tm) solution uniquely verifies identities (both social and email based identities) to prevent this type of fraud from occuring. By uniquely validating the identity associated to the email address vs. the identity associated to the social profile to verify social proof across the internet, Socure's solution can distinguish between real, synthetic and stolen identities, preventing Identity Fraud.
AI Is Everywhere, but Don't Ignore the Basics
Howie Xu, Vice President of AI and Machine Learning at Zscaler,  9/10/2019
Fed Kaspersky Ban Made Permanent by New Rules
Dark Reading Staff 9/11/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-16317
PUBLISHED: 2019-09-14
In Pimcore before 5.7.1, an attacker with limited privileges can trigger execution of a .phar file via a phar:// URL in a filename parameter, because PHAR uploads are not blocked and are reachable within the phar://../../../../../../../../var/www/html/web/var/assets/ directory, a different vulnerabi...
CVE-2019-16318
PUBLISHED: 2019-09-14
In Pimcore before 5.7.1, an attacker with limited privileges can bypass file-extension restrictions via a 256-character filename, as demonstrated by the failure of automatic renaming of .php to .php.txt for long filenames, a different vulnerability than CVE-2019-10867 and CVE-2019-16317.
CVE-2019-16307
PUBLISHED: 2019-09-14
A Reflected Cross-Site Scripting (XSS) vulnerability in the webEx module in webExMeetingLogin.jsp and deleteWebExMeetingCheck.jsp in Fuji Xerox DocuShare through 7.0.0.C1.609 allows remote attackers to inject arbitrary web script or HTML via the handle parameter (webExMeetingLogin.jsp) and meetingKe...
CVE-2019-16294
PUBLISHED: 2019-09-14
SciLexer.dll in Scintilla in Notepad++ (x64) before 7.7 allows remote code execution or denial of service via Unicode characters in a crafted .ml file.
CVE-2019-16309
PUBLISHED: 2019-09-14
FlameCMS 3.3.5 has SQL injection in account/login.php via accountName.