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
Oldest First  |  Newest First  |  Threaded View
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?
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.
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.
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).
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/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.
garrytroomen
50%
50%
garrytroomen,
User Rank: Apprentice
1/4/2017 | 11:02:02 AM
good story
Very inretesting article, thank you!


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-22392
PUBLISHED: 2021-08-05
Cross Site Scripting (XSS) vulnerability exists in Subrion CMS 4.2.2 when adding a blog and then editing an image file.
CVE-2021-3591
PUBLISHED: 2021-08-05
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Notes: none.
CVE-2021-3642
PUBLISHED: 2021-08-05
A flaw was found in Wildfly Elytron where ScramServer may be susceptible to Timing Attack if enabled. The highest threat of this vulnerability is confidentiality. This flaw affectes Wildfly Elytron versions prior to 1.10.14.Final, prior to 1.15.5.Final and prior to 1.16.1.Final.
CVE-2021-3655
PUBLISHED: 2021-08-05
A vulnerability was found in the Linux kernel in versions before v5.14-rc1. Missing size validations on inbound SCTP packets may allow the kernel to read uninitialized memory.
CVE-2021-32003
PUBLISHED: 2021-08-05
Unprotected Transport of Credentials vulnerability in SiteManager provisioning service allows local attacker to capture credentials if the service is used after provisioning. This issue affects: Secomea SiteManager All versions prior to 9.5 on Hardware.