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?


News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-30477
PUBLISHED: 2021-04-15
An issue was discovered in Zulip Server before 3.4. A bug in the implementation of replies to messages sent by outgoing webhooks to private streams meant that an outgoing webhook bot could be used to send messages to private streams that the user was not intended to be able to send messages to.
CVE-2021-30478
PUBLISHED: 2021-04-15
An issue was discovered in Zulip Server before 3.4. A bug in the implementation of the can_forge_sender permission (previously is_api_super_user) resulted in users with this permission being able to send messages appearing as if sent by a system bot, including to other organizations hosted by the sa...
CVE-2021-30479
PUBLISHED: 2021-04-15
An issue was discovered in Zulip Server before 3.4. A bug in the implementation of the all_public_streams API feature resulted in guest users being able to receive message traffic to public streams that should have been only accessible to members of the organization.
CVE-2021-30487
PUBLISHED: 2021-04-15
In the topic moving API in Zulip Server 3.x before 3.4, organization administrators were able to move messages to streams in other organizations hosted by the same Zulip installation.
CVE-2020-36288
PUBLISHED: 2021-04-15
The issue navigation and search view in Jira Server and Data Center before version 8.5.12, from version 8.6.0 before version 8.13.4, and from version 8.14.0 before version 8.15.1 allows remote attackers to inject arbitrary HTML or JavaScript via a DOM Cross-Site Scripting (XSS) vulnerability caused ...