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.

Comments
White House Announces Retaliatory Measures For Russian Election-Related Hacking
Newest First  |  Oldest First  |  Threaded View
garrytroomen
50%
50%
garrytroomen,
User Rank: Apprentice
1/4/2017 | 11:02:02 AM
good story
Very inretesting article, thank you!
RetiredUser
50%
50%
RetiredUser,
User Rank: Ninja
1/3/2017 | 6:01:53 PM
Re: Can we get real for a moment?
Joe, I meant also to note that as long as the intent of the hackers was to affect election results, we can call it an election hack.  No, the actions causing an affect on the election alone don't qualify - the intent needs to be there, too.  Why is the distinction important to me?  Because as cyberlaw matures and the criminalization of acts of hackers evolves, I think it is important to - as clearly as is possible - "properly" label acts of cybercrime.  The prupose for this is to better serve hacktivists whose crimes are based upon good-intent rather than malicious-intent (how we get the government to acknowledge hactivism as borne from "good-intent" is an entirely different conversation).  In time we want to be sure that the "time fits the crime".  Electoral manipulation by hacking needs to be more closely examined, defined and committed to the law books.  IMHO.
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
1/3/2017 | 3:21:32 PM
Re: Can we get real for a moment?
So, by that logic, the person(s) who hacked Mitt Romney's tax returns and released them in 2012 and the person(s) who hacked Donald Trump's tax returns last year were likewise hacking the election.

And nary an eyebrow was batted then.

Also, by this same logic, any email hack related to any political figure, potential political figure, or political entity (e.g., a PAC, Super PAC, political party, etc.) is necessarily an election hack -- regardless of when it takes place.  (After all, voters do have memories.)

Incidentally, I question if the ultimate end result on Election Day would have been different even without the John Podesta/HRC email leaks.
RetiredUser
50%
50%
RetiredUser,
User Rank: Ninja
1/1/2017 | 7:58:32 PM
Re: Can we get real for a moment?
I'm usually on the same page as you, Joe, but in this case I think one could argue for this being election system hacking simply from the perspective of the effect on popular opinion, the use of the incident as leverage in political arguments, etc.  However, to what extent this incident produced negative impact upon the US election process has yet to be properly measured.  But I also think that because this was not a hack upon actual voting software that could directly impact vote numbers, the event registers at the same level as any other politically-motivated spin we are used to seeing from either candidate; if and only if the hackers responsible were not hired by any US players, and no US players were resposible for motivating the hackers to do what they did (in other words, if the hack wasn't on the table before someone from the US in a significant political role "inspired" it).
michaelfillin
100%
0%
michaelfillin,
User Rank: Apprentice
1/1/2017 | 4:46:27 PM
Re: White House Announces Retaliatory Measures
"The administration, fellow lawmakers and general public must understand the potentially catastrophic consequences of a digital cyber conflict escalating into a kinetic, conventional shooting-war"

> Do you think they didn't ? Not being sarcastic, just asking.
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
12/31/2016 | 12:31:25 PM
Can we get real for a moment?
> That attack was against one entertainment company, however, and not a nation's election system

Hacking emails and giving them to Wikileaks is malicious hacking indeed -- but it is NOT hacking a nation's election system.
Lefty_John
50%
50%
Lefty_John,
User Rank: Apprentice
12/30/2016 | 10:19:36 AM
Donald Trump
What did Trump know and when did he know it?


COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.