Risk
2/12/2009
05:39 PM
Connect Directly
LinkedIn
Twitter
Google+
RSS
E-Mail
50%
50%

25 Things Facebook Couldn't Keep Secret In Court

Redacted portions of a PDF transcript from a court hearing to determine Facebook's settlement with ConnectU were revealed.

Facebook has become the latest company to be bitten by bad PDF redaction.

The company's confidential settlement of a lawsuit brought by ConnectU was revealed Wednesday when Associated Press writer Michael Liedtke reported that redacted portions of a PDF transcript of a court hearing, at which details of the settlement were discussed, could be easily revealed.

"Large portions of that hearing are redacted in a transcript of the June hearing, but The Associated Press was able to read the blacked-out portions by copying from an electronic version of the document and pasting the results into another document," Liedtke wrote in his article.

The improperly redacted document revealed that ConnectU received somewhere between from $31 million and $65 million to settle its lawsuit, and that Facebook's internal valuation was about $3.7 billion.

"At some point in the document's workflow, it appears that someone added a white rectangle over white text in order to cover it," said David Stromfeld, a senior product manager for Adobe Acrobat. "And that's what they thought was sufficient to make that content undiscoverable."

That's not the right way to redact content.

Such mistakes have bedeviled would-be censors for years, in PDF files and Microsoft Word files, too.

A document on proper redaction technique, published by the National Security Agency in December 2005, describes the problem thus: "Both the Microsoft Word document format (MS Word) and Adobe Portable Document (PDF) are complex, sophisticated computer data formats. They can contain many kinds of information such as text, graphics, tables, images, meta-data, and more all mixed together. The complexity makes them potential vehicles for exposing information unintentionally, especially when downgrading or sanitizing classified materials."

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Latest Comment: nice one
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-2015-0845
Published: 2015-04-17
Format string vulnerability in Movable Type Pro, Open Source, and Advanced before 5.2.13 and Pro and Advanced 6.0.x before 6.0.8 allows remote attackers to execute arbitrary code via vectors related to localization of templates.

CVE-2015-1318
Published: 2015-04-17
The crash reporting feature in Apport 2.13 through 2.17.x before 2.17.1 allows local users to gain privileges via a crafted usr/share/apport/apport file in a namespace (container).

CVE-2015-1852
Published: 2015-04-17
The s3_token middleware in OpenStack keystonemiddleware before 1.6.0 and python-keystoneclient before 1.4.0 disables certification verification when the "insecure" option is set in a paste configuration (paste.ini) file regardless of the value, which allows remote attackers to conduct man-in-the-mid...

CVE-2015-1856
Published: 2015-04-17
OpenStack Object Storage (Swift) before 2.3.0, when allow_version is configured, allows remote authenticated users to delete the latest version of an object by leveraging listing access to the x-versions-location container.

CVE-2013-4866
Published: 2015-04-16
The LIXIL Corporation My SATIS Genius Toilet application for Android has a hardcoded Bluetooth PIN, which allows physically proximate attackers to trigger physical resource consumption (water or heat) or user discomfort.

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.