Risk
2/12/2013
01:08 PM
50%
50%

Flickr Bug Revealed Private Photos To Public

Yahoo-owned Flickr's fix -- resetting permissions on all potentially affected images -- also broke some connections with third-party websites.

The online photo-sharing service Flickr shared more photographs than it was supposed to.

Flickr, which is owned by Yahoo, emailed some users this past weekend to warn them that some of their photos marked "private" were instead made publicly available: "While performing routine site maintenance, we identified a software bug that may have changed the view setting on some of your photos from non-public (i.e., private or viewable only by family and friends) to public," according to the Flickr email, which was signed by Flickr VP Brett Wayn. "The affected photos were visible on Flickr between January 18th and February 7th, 2013."

"We're deeply sorry this happened," said Wayn. "We've put in place a number of additional measures to prevent this from happening again."

The bug affected some images uploaded between April and December 2012. "Overall, this issue impacted only a small percentage of photos," according to Wayn's email. On average, however, 1.4 million photos marked "public" were uploaded to Flickr daily in 2012, meaning that tens of millions of private photos could have been made public.

[ Third-party integration is convenient, but it can be risky, too. See Facebook Login Bug: Lessons Learned. ]

Yahoo didn't immediately respond to emailed questions about how many Flickr users were affected, how many images were exposed or whether Yahoo has finished contacting all affected users by email. In addition, "Flickr was unable to tell me if anyone actually did see my private photos, when I asked," reported paid Flickr account holder Barry Schwartz, who's the CEO of RustyBrick and news editor of Search Engine Land, and who received a "Dear Barry" letter from Flickr.

Flickr's email noted that none of the affected images were displayed by Flickr's own search engine or allowed to be indexed by third-party search engines. But the affected images would have been viewable when visiting an affected user's Flickr "photostream," or browsing to the image via a link.

As a precautionary measure, Flickr set the "who can see this photo?" settings for any potentially affected image to "private." But that blanket change means any public images that were embedded in third-party websites, or linked to from other websites, now display a broken link. Multiple affected users have taken to the Flickr help forum to complain that they have to manually review all of their images to try and spot the ones that are now marked as private, but which should really be public.

Flickr recently appeared to get a new lease on life after Google product development VP Marissa Mayer last year assumed the helm of Yahoo, and pushed Yahoo product upgrades, including a revamped mobile Flickr app.

But this isn't the only recently discovered Yahoo privacy or data security snafu. The company was already in the news this week after information security journalist Brian Krebs reported Monday that Yahoo's free, consumer-focused website building tool, SiteBuilder, which runs on Windows, bundles a "dangerously insecure" version of Java that dates from summer 2008.

The most recent version of Java 6 is update 39, which includes fixes for numerous vulnerabilities in older Java 6 versions that are actively targeted by attackers, oftentimes via automated crimeware toolkits. For comparison's sake, the version of Java bundled with SiteBuilder is Java 6 Update 7, which was released more than four years ago. As a result, anyone who uses SiteBuilder but fails to update the included Java software is putting their PC at risk of being compromised.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-9728
Published: 2015-08-31
The UDF filesystem implementation in the Linux kernel before 3.18.2 does not validate certain lengths, which allows local users to cause a denial of service (buffer over-read and system crash) via a crafted filesystem image, related to fs/udf/inode.c and fs/udf/symlink.c.

CVE-2014-9729
Published: 2015-08-31
The udf_read_inode function in fs/udf/inode.c in the Linux kernel before 3.18.2 does not ensure a certain data-structure size consistency, which allows local users to cause a denial of service (system crash) via a crafted UDF filesystem image.

CVE-2014-9730
Published: 2015-08-31
The udf_pc_to_char function in fs/udf/symlink.c in the Linux kernel before 3.18.2 relies on component lengths that are unused, which allows local users to cause a denial of service (system crash) via a crafted UDF filesystem image.

CVE-2014-9731
Published: 2015-08-31
The UDF filesystem implementation in the Linux kernel before 3.18.2 does not ensure that space is available for storing a symlink target's name along with a trailing \0 character, which allows local users to obtain sensitive information via a crafted filesystem image, related to fs/udf/symlink.c and...

CVE-2015-0942
Published: 2015-08-31
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2015-6742, CVE-2015-6743, CVE-2015-6744, CVE-2015-6745, CVE-2015-6746, CVE-2015-6747. Reason: This candidate originally combined multiple issues that have different vulnerability types and other complex abstraction issues. Notes: All CV...

Dark Reading Radio
Archived Dark Reading Radio
Another Black Hat is in the books and Dark Reading was there. Join the editors as they share their top stories, biggest lessons, and best conversations from the premier security conference.