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.

Application Security

5/29/2019
10:40 AM
50%
50%

Flipboard Confirms Two Hacks, Prompts Password Resets

The company reports two incidents affected a subset of its users and is resetting passwords for involved accounts.

Flipboard, a news aggregator and content-sharing platform, has confirmed two separate security incidents in which unauthorized attackers broke into some of its databases.

The company launched a breach investigation on April 23, when it learned these databases had been hacked. It found someone had accessed, and potentially obtained copies of, databases with user information between June 2, 2018, and March 23, 2019, as well as April 21-22, 2019.

These databases stored account information belonging to a subset of Flipboard's 150 million users; the company has not disclosed the total number of people affected. Compromised data includes names, Flipboard usernames, email addresses, passwords, and digital tokens used to connect Flipboard accounts to third-party accounts like Facebook or Google. Flipboard does not collect government-issued IDs or payment card, bank account, or any other financial data.

"Not all Flipboard users' account information was involved in the incident," officials report in a blog post. "We're still identifying the accounts involved and as a precaution, we reset all users' passwords and replaced or deleted all digital tokens." The company also says there is no evidence indicating attackers used digital tokens to access users' third-party accounts.

Flipboard does note the passwords were never stored in plaintext. Those created or changed after March 14, 2012, were cryptographically protected with the bcrypt function. Passwords created before then were salted and hashed with SHA-1, officials say in the blog post.

Owners of compromised accounts can continue to use Flipboard on devices where they're already logged in. When Flipboard is accessed from a new device, or someone logs out of Flipboard on their current device, they'll be asked to create a new password when they log in.

Read more details here.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
5/31/2019 | 10:10:49 AM
....they'll be asked
Forced PW change needs to be a requirement in instances like this. The fact that if you are already logged into a device it will not require you to change pw and re-authenticate is alarming. Second, it makes me wary that you will be prompted but not forced. As a society a large commonality is that we treat prompts like noise and just ignore them and push them to the side until forced.
The Security of Cloud Applications
Hillel Solow, CTO and Co-founder, Protego,  7/11/2019
Where Businesses Waste Endpoint Security Budgets
Kelly Sheridan, Staff Editor, Dark Reading,  7/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
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
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-13643
PUBLISHED: 2019-07-18
Stored XSS in EspoCRM before 5.6.4 allows remote attackers to execute malicious JavaScript and inject arbitrary source code into the target pages. The attack begins by storing a new stream message containing an XSS payload. The stored payload can then be triggered by clicking a malicious link on the...
CVE-2019-13644
PUBLISHED: 2019-07-18
Firefly III before 4.7.17.1 is vulnerable to stored XSS due to lack of filtration of user-supplied data in a budget name. The JavaScript code is contained in a transaction, and is executed on the tags/show/$tag_number$ tag summary page.
CVE-2019-13645
PUBLISHED: 2019-07-18
Firefly III before 4.7.17.3 is vulnerable to stored XSS due to lack of filtration of user-supplied data in image file names. The JavaScript code is executed during attachments/edit/$file_id$ attachment editing.
CVE-2019-13646
PUBLISHED: 2019-07-18
Firefly III before 4.7.17.3 is vulnerable to reflected XSS due to lack of filtration of user-supplied data in a search query.
CVE-2019-13647
PUBLISHED: 2019-07-18
Firefly III before 4.7.17.3 is vulnerable to stored XSS due to lack of filtration of user-supplied data in image file content. The JavaScript code is executed during attachments/view/$file_id$ attachment viewing.