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
Russia Likely Behind DNC Breach, Says FBI
Oldest First  |  Newest First  |  Threaded View
RyanSepe
RyanSepe,
User Rank: Ninja
7/26/2016 | 4:44:41 PM
Unsure of Motive
I think the motive behind which these attacks were committed is unclear. For the reasons stated, the opposing candidates approval for Putin and disapproval towards NATO is not a strong leg to stand on and sounds like complete speculation.
dougw426
dougw426,
User Rank: Apprentice
7/27/2016 | 4:05:55 PM
Re: Unsure of Motive
I think the only motive that isn't speculation is that of exposing the truth.
RyanSepe
RyanSepe,
User Rank: Ninja
7/28/2016 | 5:35:40 PM
Re: Unsure of Motive
In many cases I would agree with you. This is one such case. But once more variables are provided, motive can be more easily discerned. I don't think there are enough known parameters in this case for the motive not to be speculative.
dougw426
dougw426,
User Rank: Apprentice
7/29/2016 | 9:00:20 AM
Re: Unsure of Motive
I think there is no doubt the Assange has an axe to grind. Outside of that I agree with you.
JulietteRizkallah
JulietteRizkallah,
User Rank: Ninja
7/31/2016 | 1:12:33 AM
Re: Unsure of Motive
Regardless of motive, i am surprised of the lax of the DNC. We have been trained in the corporate world to assume that any of our emails could become public (or be viewed by others than the ones first intended since all corporate emails belong to the company) and to write and express opinions accordingly.  Surprisingly, in the polical world this was not the norm...maybe they thought they could just delete emails...


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
Creating an Effective Incident Response Plan
Security teams are realizing their organizations will experience a cyber incident at some point. An effective incident response plan that takes into account their specific requirements and has been tested is critical. This issue of Tech Insights also includes: -a look at the newly signed cyber-incident law, -how organizations can apply behavioral psychology to incident response, -and an overview of the Open Cybersecurity Schema Framework.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-4194
PUBLISHED: 2022-11-30
Use after free in Accessibility in Google Chrome prior to 108.0.5359.71 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Medium)
CVE-2022-4195
PUBLISHED: 2022-11-30
Insufficient policy enforcement in Safe Browsing in Google Chrome prior to 108.0.5359.71 allowed a remote attacker to bypass Safe Browsing warnings via a malicious file. (Chromium security severity: Medium)
CVE-2022-4175
PUBLISHED: 2022-11-30
Use after free in Camera Capture in Google Chrome prior to 108.0.5359.71 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
CVE-2022-4176
PUBLISHED: 2022-11-30
Out of bounds write in Lacros Graphics in Google Chrome on Chrome OS and Lacros prior to 108.0.5359.71 allowed a remote attacker who convinced a user to engage in specific UI interactions to potentially exploit heap corruption via UI interactions. (Chromium security severity: High)
CVE-2022-4177
PUBLISHED: 2022-11-30
Use after free in Extensions in Google Chrome prior to 108.0.5359.71 allowed an attacker who convinced a user to install an extension to potentially exploit heap corruption via a crafted Chrome Extension and UI interaction. (Chromium security severity: High)