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
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-0103
Published: 2014-07-29
WebAccess in Zarafa before 7.1.10 and WebApp before 1.6 stores credentials in cleartext, which allows local Apache users to obtain sensitive information by reading the PHP session files.

CVE-2014-0475
Published: 2014-07-29
Multiple directory traversal vulnerabilities in GNU C Library (aka glibc or libc6) before 2.20 allow context-dependent attackers to bypass ForceCommand restrictions and possibly have other unspecified impact via a .. (dot dot) in a (1) LC_*, (2) LANG, or other locale environment variable.

CVE-2014-0889
Published: 2014-07-29
Multiple cross-site scripting (XSS) vulnerabilities in IBM Atlas Suite (aka Atlas Policy Suite), as used in Atlas eDiscovery Process Management through 6.0.3, Disposal and Governance Management for IT through 6.0.3, and Global Retention Policy and Schedule Management through 6.0.3, allow remote atta...

CVE-2014-2226
Published: 2014-07-29
Ubiquiti UniFi Controller before 3.2.1 logs the administrative password hash in syslog messages, which allows man-in-the-middle attackers to obtains sensitive information via unspecified vectors.

CVE-2014-3020
Published: 2014-07-29
install.sh in the Embedded WebSphere Application Server (eWAS) 7.0 before FP33 in IBM Tivoli Integrated Portal (TIP) 2.1 and 2.2 sets world-writable permissions for the installRoot directory tree, which allows local users to gain privileges via a Trojan horse program.

Best of the Web
Dark Reading Radio