Attacks/Breaches

2/9/2018
12:15 PM
50%
50%

Sacramento Bee Databases Hit with Ransomware Attack

The Bee did not pay ransom and deleted its databases to prevent future attacks, according to its publisher.

The Sacramento Bee reported that two of its databases, both on a third-party server, were hit with a ransomware attack in January 2017. A Bee employee discovered the attack last week following a tip from a reporter with a different organization, the publication reports.

One affected database contained California voter registration data from the California Secretary of State and was obtained for reporting purposes. Another, a subscriber database, contained contact data for 53,000 current and former Bee subscribers who activated digital accounts before 2017. The Bee is informing those whose names, addresses, email addresses, and phone numbers were compromised.

Publisher Gary Wortel reports neither database contained credit card numbers, bank account data, or Social Security numbers. The voter registration data had been previously exposed online, and the same database had been shared with organizations that had been subject to attack.

An anonymous attacker demanded a Bitcoin ransom in exchange for the data. The Bee chose not to pay and has deleted both databases to prevent further attacks.

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
alphaa10
50%
50%
alphaa10,
User Rank: Strategist
2/17/2018 | 12:23:13 AM
Re: Profound solution?
The measure announced was not to recover the lost data, but to frustrate inevitable future attempts to make the same threat, perhaps with more damage. Once a ransom demand is met, there is nothing to dissuade the same or similar groups from another attack.

Did the newspaper promise a return to paper records? Not at all, but simply a more layered and distributed system, with multiple checkpoints.

Under the circumstances, the Bee declaration helps the newspaper isolate itself from further extortion attempts.

 
BrianN060
50%
50%
BrianN060,
User Rank: Ninja
2/12/2018 | 6:07:58 PM
Looking for correlations
@DR staff: Elements of this story are repeated in any number of cybersecurity articles, surveys, reports, etc..  What I haven't seen is analysis on how specific data storage choices correlate with attack frequency, type, detection, and other characteristics and metrics. 

In this story "...its databases, both on a third-party server...", raises the above questions as regards to use of third party servers; but also leads to questions about attacks and the specifics of type, location, infrastructure, etc.., of such servers. 

Perhaps what I'm looking for is a multidimensional map showing just what particular dangers are known to inhabit various (metaphorical as well as actual), regions.  In other words, are there safer places and containers to bury your treasure? 

I realize this is far from a simple question.  For starters, a single vendor might offer several types of relational and non-relational patterns and management options; and might have options for restricting use to certain geo-located datacenters - and a single organization might use different options, from different vendors, as well as combine public-cloud with in-house storage options. 

Is anyone work on this type of multi-factor threat assessment for data storage choices? 
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
2/12/2018 | 3:14:51 PM
Profound solution?
The database data is deleted to prevent future theft.  Wow!!!!   What an idea.  Lock the barn door after the theft is done.  Brilliant.  Of course, the data is already out there so who ares about deletion.  Hey, shore up the walls would be a good idea too.  
Google Engineering Lead on Lessons Learned From Chrome's HTTPS Push
Kelly Sheridan, Staff Editor, Dark Reading,  8/8/2018
Election Websites, Backend Systems Most at Risk of Cyberattack in Midterms
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/14/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-8405
PUBLISHED: 2018-08-15
An elevation of privilege vulnerability exists when the DirectX Graphics Kernel (DXGKRNL) driver improperly handles objects in memory, aka "DirectX Graphics Kernel Elevation of Privilege Vulnerability." This affects Windows Server 2012 R2, Windows RT 8.1, Windows Server 2016, Windows 8.1, ...
CVE-2018-8406
PUBLISHED: 2018-08-15
An elevation of privilege vulnerability exists when the DirectX Graphics Kernel (DXGKRNL) driver improperly handles objects in memory, aka "DirectX Graphics Kernel Elevation of Privilege Vulnerability." This affects Windows Server 2016, Windows 10, Windows 10 Servers. This CVE ID is unique...
CVE-2018-8412
PUBLISHED: 2018-08-15
An elevation of privilege vulnerability exists when the Microsoft AutoUpdate (MAU) application for Mac improperly validates updates before executing them, aka "Microsoft (MAU) Office Elevation of Privilege Vulnerability." This affects Microsoft Office.
CVE-2018-8414
PUBLISHED: 2018-08-15
A remote code execution vulnerability exists when the Windows Shell does not properly validate file paths, aka "Windows Shell Remote Code Execution Vulnerability." This affects Windows 10 Servers, Windows 10.
CVE-2018-8398
PUBLISHED: 2018-08-15
An information disclosure vulnerability exists when the Windows GDI component improperly discloses the contents of its memory, aka "Windows GDI Information Disclosure Vulnerability." This affects Windows 7, Windows Server 2012 R2, Windows RT 8.1, Windows Server 2008, Windows Server 2012, W...