Risk
7/3/2012
11:57 AM
50%
50%

Facebook To Fix Smartphone Email Snafu

Android and iOS users report some contacts are being forcibly updated to an "@facebook.com" email address.

5 Social Networks To Achieve 10 Business Tasks
5 Social Networks To Achieve 10 Business Tasks
(click image for larger view and for slideshow)
Have your smartphone contacts' email addresses been automatically updated to make their "@facebook.com" email addresses the new default? If so, you're not alone.

"Some smartphone users, particularly those using older Android devices, are reporting that their on-phone address books have been silently updated to make @facebook.com email addresses the default way to send a message to their contacts," said Graham Cluley, senior technology consultant at Sophos, Tuesday in a blog post.

Some iOS 6 beta testers have reported similar issues. "This is presumably because one of iOS 6's features is greater synchronization for the iPhone/iPad with Facebook," he said.

[ Despite its disappointing IPO, does Facebook have potential for future greatness? Read more at The Second Coming Of Facebook. ]

Related bug reports have been appearing recently on online forums. "This morning my mother was complaining that many of the email addresses in her Droid Razr contacts had been replaced with Facebook ones," read one such post to Hacker News. "It would seem the Facebook app had been populating her address book with emails and contact photos and decided to migrate all her Facebook-using contacts over to this convenient new system."

Tuesday, a Facebook spokeswoman confirmed that the social network is working on a fix for two problems--one involving synchronizing contacts on mobile devices, and another relating to Facebook Messaging.

In terms of contact synchronization, which is performed using an API, the spokeswoman said via email, "For most devices, we've verified that the API is working correctly and pulling the primary email address associated with the users' Facebook account. However, for people on certain devices, a bug meant that the device was pulling the last email address added to the account rather than the primary email address, resulting in @facebook.com addresses being pulled."

"We are in the process of fixing this issue and it will be resolved soon," she continued. "After that, those specific devices should pull the correct addresses."

Meanwhile, Facebook is also working to resolve a messaging-related issue that could result in people's Facebook messages going undelivered, without the sender receiving a notification that the message hadn't been delivered. "If someone sends you an email to your @facebook.com email address and it's from an address associated with a Facebook friend or friend of friend's accounts, it will go into the inbox," the Facebook spokeswoman said. "If it's from an address not associated with a friend or friend of friend's Facebook account, it will go into your other folder. However, if you've specified in privacy settings that you only want to receive messages from friends or friend of friends, then the message will bounce." "We've noticed that in a very limited number of cases, the bounce e-mail back to the original sender may not be delivered because it may get intercepted by spam filters," she said. "We are working to make sure that e-mail senders consistently receive bounce messages."

Pending fixes aside, Sophos' Cluley advised all Facebook users to review which of their email addresses the social network is currently listing, especially in the wake of Facebook recently changing all users' default email addresses to "@facebook.com" based on the URL of their public profile. "I would still strongly recommend checking that you are happy with what email addresses (if any) you are showing on your Facebook profile, and whether you want to sync your smartphone's address book with the site," he said.

New apps promise to inject social features across entire workflows, raising new problems for IT. In the new, all-digital Social Networking issue of InformationWeek, find out how companies are making social networking part of the way their employees work. Also in this issue: How to better manage your video data. (Free with registration.)

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
ANON1245867443530
50%
50%
ANON1245867443530,
User Rank: Apprentice
7/4/2012 | 2:38:26 AM
re: Facebook To Fix Smartphone Email Snafu
Yeah, that's what happens when you give personal data to inept bunglers like Facebook. This policy alone should've made it clear that we're dealing with amateur hour: http://goldmanosi.blogspot.com...
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2011-4403
Published: 2015-04-24
Multiple cross-site request forgery (CSRF) vulnerabilities in Zen Cart 1.3.9h allow remote attackers to hijack the authentication of administrators for requests that (1) delete a product via a delete_product_confirm action to product.php or (2) disable a product via a setflag action to categories.ph...

CVE-2012-2930
Published: 2015-04-24
Multiple cross-site request forgery (CSRF) vulnerabilities in TinyWebGallery (TWG) before 1.8.8 allow remote attackers to hijack the authentication of administrators for requests that (1) add a user via an adduser action to admin/index.php or (2) conduct static PHP code injection attacks in .htusers...

CVE-2012-2932
Published: 2015-04-24
Multiple cross-site scripting (XSS) vulnerabilities in TinyWebGallery (TWG) before 1.8.8 allow remote attackers to inject arbitrary web script or HTML via the (1) selitems[] parameter in a copy, (2) chmod, or (3) arch action to admin/index.php or (4) searchitem parameter in a search action to admin/...

CVE-2012-5451
Published: 2015-04-24
Multiple stack-based buffer overflows in HttpUtils.dll in TVMOBiLi before 2.1.0.3974 allow remote attackers to cause a denial of service (tvMobiliService service crash) via a long string in a (1) GET or (2) HEAD request to TCP port 30888.

CVE-2015-0297
Published: 2015-04-24
Red Hat JBoss Operations Network 3.3.1 does not properly restrict access to certain APIs, which allows remote attackers to execute arbitrary Java methos via the (1) ServerInvokerServlet or (2) SchedulerService or (3) cause a denial of service (disk consumption) via the ContentManager.

Dark Reading Radio
Archived Dark Reading Radio
Join security and risk expert John Pironti and Dark Reading Editor-in-Chief Tim Wilson for a live online discussion of the sea-changing shift in security strategy and the many ways it is affecting IT and business.