Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

Twitter, Feds Settle Security Charges

Twitter must establish and maintain a "comprehensive information security program" and allow third-party review of the program biannually for the 10 years.

Twitter has settled Federal Trade Commission charges that the social network put users' personal information at risk, while deceiving them about safeguards to protect data.

The settlement, announced Thursday, closed the FTC's first action against a social networking site for faulty security. Twitter's failings led to two well-publicized attacks, one of which resulted in a hacker gaining access to several high-profile accounts, including that of then President-elect Barack Obama.

The settlement requires Twitter to take a number of security steps to protect user data, steps the site said it has already taken. "Even before the agreement, we'd implemented many of the FTC's suggestions and the agreement formalizes our commitment to those security practices," Twitter said in response to the FTC's settlement announcement.

Nevertheless, the FTC said Twitter failed to provide the security it promised users.

"When a company promises consumers that their personal information is secure, it must live up to that promise," David Vladeck, director of the FTC's Bureau of Consumer Protection, said in a statement. "Likewise, a company that allows consumers to designate their information as private must use reasonable security to uphold such designations."

The first security breach occurred in January 2009 when a hacker used an automated password-generation tool to continuously try to log in to a person's account. In some cases, the hacker made thousands of attempts before striking pay dirt. Twitter's culpability was in failing to implement password rules that would have led to stronger passwords, the FTC said. In addition, Twitter should have had technology in place to lock out the hacker after several failed attempts.

The hacker accessed the accounts of 45 Twitter users, including Facebook, Fox News, The Huffington Post, Obama, Britney Spears and CNN host Rick Sanchez. In some cases, the hacker sent phony tweets under the accounts. Tweets are the short messages of 140 characters or less people broadcast to followers on the site.

A bogus tweet sent from Obama's account offered his more than 150,000 followers a chance to win $500 in free gasoline, according to the FTC.

The second breach occurred in April 2009 when a hacker broke into a Twitter employee's administrative account by first accessing the employee's Yahoo e-mail account, where the password was stored in plain text.

In gaining access to the administrative account, the hacker could access private information from any Twitter user, according to the FTC. The hacker did post more than a dozen screenshots of Twitter's administrative console on several Web sites.

To help prevent the second breach, Twitter should have prohibited employees from storing passwords within personal e-mail accounts, enforced periodic changes of administrative passwords, restricted access to administrative controls to employees whose jobs required it and imposed other reasonable restrictions on administrative access, the FTC said.

Under the terms of the settlement. Twitter is barred for 20 years from misleading users about the extent to which it protects their privacy and personal information. The company also must establish and maintain a "comprehensive information security program," the FTC said. A third party has to assess the program every other year for 10 years.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Florida Town Pays $600K to Ransomware Operators
Curtis Franklin Jr., Senior Editor at Dark Reading,  6/20/2019
Pledges to Not Pay Ransomware Hit Reality
Robert Lemos, Contributing Writer,  6/21/2019
AWS CISO Talks Risk Reduction, Development, Recruitment
Kelly Sheridan, Staff Editor, Dark Reading,  6/25/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-10133
PUBLISHED: 2019-06-26
A flaw was found in Moodle before 3.7, 3.6.4, 3.5.6, 3.4.9 and 3.1.18. The form to upload cohorts contained a redirect field, which was not restricted to internal URLs.
CVE-2019-10134
PUBLISHED: 2019-06-26
A flaw was found in Moodle before 3.7, 3.6.4, 3.5.6, 3.4.9 and 3.1.18. The size of users' private file uploads via email were not correctly checked, so their quota allowance could be exceeded.
CVE-2019-10154
PUBLISHED: 2019-06-26
A flaw was found in Moodle before versions 3.7, 3.6.4. A web service fetching messages was not restricted to the current user's conversations.
CVE-2019-9039
PUBLISHED: 2019-06-26
The Couchbase Sync Gateway 2.1.2 in combination with a Couchbase Server is affected by a previously undisclosed N1QL-injection vulnerability in the REST API. An attacker with access to the public REST API can insert additional N1QL statements through the parameters ?startkey? and ?endkey? of the ?_a...
CVE-2018-20846
PUBLISHED: 2019-06-26
Out-of-bounds accesses in the functions pi_next_lrcp, pi_next_rlcp, pi_next_rpcl, pi_next_pcrl, pi_next_rpcl, and pi_next_cprl in openmj2/pi.c in OpenJPEG through 2.3.0 allow remote attackers to cause a denial of service (application crash).