Risk
9/1/2009
02:39 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Researcher Launches Facebook Bug Project For September

Several of the most popular applications on the social network contain easy-to-exploit cross-site scripting (XSS) flaws

First Twitter and now Facebook: A researcher today began a round of daily disclosures of serious vulnerabilities in popular Facebook applications.

The researcher, who goes by "theharmonyguy," plans to disclose multiple cross-site scripting (XSS) flaws he discovered in various third-party Facebook applications this month, though he may not do so every day. He says he found major security holes in several of Facebook's top 10 most popular applications.

Today's bugs include XSSes in FunSpace, which has more than 8 million users; SuperPoke, which has 2 million users; SocialToo, which has nearly 2,000 users; and YellowPages.ca, which has nearly 1,200 users. FunSpace, SuperPoke, and SocialToo have been patched, but YellowPages.ca has not.

Theharmonyguy says Facebook's own applications tend to be secure, as does its site. He says he has studied several Facebook-written apps for the site, and it was tough to find any holes. "They seem to know what they're doing with security," he says. "I found a cross-site scripting hole on the Facebook page and contacted them, and they patched if really quickly," he says.

Even so, the researcher says Facebook doesn't vet third-party apps. "In fact, four of the five apps I'm going to post in the next week or so are Facebook-verified ones," he says.

Theharmonyguy plans to release source code for the attacks once he has completed the disclosures. He says he gives each application developer 24 hours notice before posting the flaws.

The problem, he says, lays in Facebook's API -- problem that has been well-documented by other researchers, as well. The API gives the application developer full access to a Facebook member's profile when a user runs that application.

"A lot of the security problems I and others are finding [on social networks] seem to come in through third-party apps," theharmonyguy says. "Once you start allowing this third-party content, you start opening yourself up to problems."

Theharmonyguy says XSS is simple to exploit in a Facebook application by inserting iFrames or scripts. And the XSS hole can then open the door to cross-site request forgery (CSRF) attacks, as well, he says.

There's no surefire way for Facebook users to protect themselves from these application-borne attacks, he says. "My No. 1 tip to users would be not to put anything on their profile that they don't want to be public. Treat your Facebook profile as if it's already public," he says. "And be careful what applications you install," even though Facebook-verified ones can also be abused, he says.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message. Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6335
Published: 2014-08-26
The Backup-Archive client in IBM Tivoli Storage Manager (TSM) for Space Management 5.x and 6.x before 6.2.5.3, 6.3.x before 6.3.2, 6.4.x before 6.4.2, and 7.1.x before 7.1.0.3 on Linux and AIX, and 5.x and 6.x before 6.1.5.6 on Solaris and HP-UX, does not preserve file permissions across backup and ...

CVE-2014-0480
Published: 2014-08-26
The core.urlresolvers.reverse function in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not properly validate URLs, which allows remote attackers to conduct phishing attacks via a // (slash slash) in a URL, which triggers a scheme-relative URL ...

CVE-2014-0481
Published: 2014-08-26
The default configuration for the file upload handling system in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 uses a sequential file name generation process when a file with a conflicting name is uploaded, which allows remote attackers to cause a d...

CVE-2014-0482
Published: 2014-08-26
The contrib.auth.middleware.RemoteUserMiddleware middleware in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3, when using the contrib.auth.backends.RemoteUserBackend backend, allows remote authenticated users to hijack web sessions via vectors relate...

CVE-2014-0483
Published: 2014-08-26
The administrative interface (contrib.admin) in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not check if a field represents a relationship between models, which allows remote authenticated users to obtain sensitive information via a to_field ...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Three interviews on critical embedded systems and security, recorded at Black Hat 2014 in Las Vegas.