Perimeter

Guest Blog // Selected Security Content Provided By Sophos
What's This?
6/23/2009
04:50 AM
Graham Cluley
Graham Cluley
Security Insights
50%
50%

Private Facebook Info Exposed By Simple Hack

Facebook's security has been called into question after the creators of a new blog discovered a hack that can expose private profile information of any user.

Facebook's security has been called into question after the creators of a new blog discovered a hack that can expose private profile information of any user.The creators of a new blog called FBHive showed how they could see everything listed in a Facebook user's "Basic Information" panel, regardless of the privacy settings they had chosen.

Using the security hole, they were able to view personal information about Facebook CEO Mark Zuckerberg, Digg founder Kevin Rose, and popular blogger Cory Doctorow. Of course, personal data, such as your date of birth, can be valuable information for identity thieves.

The folks at FBHive went public with proof that they had exploited the security flaw by posting screenshots of the Internet celebrities' details, seemingly frustrated that after waiting more than two weeks, Facebook had still not patched the flaw.

These screenshots have now been (quite rightly) obfuscated to protect the identities of the peopleconcerned, and Facebook has now fixed the vulnerability.

FBHive published a short video demonstrating how they were able to exploit the flaw to examine a user's profile.

It's great that Facebook has now fixed this flaw, but disturbing that the vulnerability existed in the first place -- millions of Facebook users potentially could have been in danger of having information snatched that they believed was secure.

Of course, this isn't the first time Facebook has found itself in the spotlight for not properly securing its users' information. Just last month, a security loophole was found that could have allowed identity thieves and spammers to gather users' personal email addresses.

And last year I stumbled across a security hole in the social networking site (demonstrated in the video below) that exposed every member's full date of birth, regardless of their security settings.

Facebook revealed dates of birth of users, even if they are 'hidden' from SophosLabs on Vimeo.

Maybe people need to learn that if they really want to be secure on social networks, they shouldn't rely on the Website keeping their date safe and sound -- that maybe it's better not to upload any personal information in the first place.

After all, do you really need to tell Facebook your real date of birth?

Graham Cluley is senior technology consultant at Sophos, and has been working in the computer security field since the early 1990s. When he's not updating his other blog on the Sophos website you can find him on Twitter at @gcluley. Special to Dark Reading.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Want Your Daughter to Succeed in Cyber? Call Her John
John De Santis, CEO, HyTrust,  5/16/2018
New Mexico Man Sentenced on DDoS, Gun Charges
Dark Reading Staff 5/18/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-11354
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, the IEEE 1905.1a dissector could crash. This was addressed in epan/dissectors/packet-ieee1905.c by making a certain correction to string handling.
CVE-2018-11355
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, the RTCP dissector could crash. This was addressed in epan/dissectors/packet-rtcp.c by avoiding a buffer overflow for packet status chunks.
CVE-2018-11356
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the DNS dissector could crash. This was addressed in epan/dissectors/packet-dns.c by avoiding a NULL pointer dereference for an empty name in an SRV record.
CVE-2018-11357
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the LTP dissector and other dissectors could consume excessive memory. This was addressed in epan/tvbuff.c by rejecting negative lengths.
CVE-2018-11358
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the Q.931 dissector could crash. This was addressed in epan/dissectors/packet-q931.c by avoiding a use-after-free after a malformed packet prevented certain cleanup.