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
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-2013-6501
Published: 2015-03-30
The default soap.wsdl_cache_dir setting in (1) php.ini-production and (2) php.ini-development in PHP through 5.6.7 specifies the /tmp directory, which makes it easier for local users to conduct WSDL injection attacks by creating a file under /tmp with a predictable filename that is used by the get_s...

CVE-2014-9209
Published: 2015-03-30
Untrusted search path vulnerability in the Clean Utility application in Rockwell Automation FactoryTalk Services Platform before 2.71.00 and FactoryTalk View Studio 8.00.00 and earlier allows local users to gain privileges via a Trojan horse DLL in an unspecified directory.

CVE-2014-9652
Published: 2015-03-30
The mconvert function in softmagic.c in file before 5.21, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not properly handle a certain string-length field during a copy of a truncated version of a Pascal string, which might allow remote atta...

CVE-2014-9653
Published: 2015-03-30
readelf.c in file before 5.22, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not consider that pread calls sometimes read only a subset of the available data, which allows remote attackers to cause a denial of service (uninitialized memory ...

CVE-2014-9705
Published: 2015-03-30
Heap-based buffer overflow in the enchant_broker_request_dict function in ext/enchant/enchant.c in PHP before 5.4.38, 5.5.x before 5.5.22, and 5.6.x before 5.6.6 allows remote attackers to execute arbitrary code via vectors that trigger creation of multiple dictionaries.

Dark Reading Radio
Archived Dark Reading Radio
Good hackers--aka security researchers--are worried about the possible legal and professional ramifications of President Obama's new proposed crackdown on cyber criminals.