Vulnerabilities / Threats

7/29/2016
02:00 PM
Steve Zurier
Steve Zurier
Slideshows
Connect Directly
Twitter
RSS
E-Mail
100%
0%

5 Things We Know So Far About The DNC Hack

The plot thickens this week as Donald Trump openly calls on Russia to release Hillary Clinton's emails. All roads appear to lead to Russia in the DNC -- and now possibly the DCCC -- hacks.
Previous
1 of 6
Next

Image Source: www.wibw.com

Image Source: www.wibw.com

It’s interesting to hear different opinions on the Democratic National Committee (DNC) hack and other politically-motivated hacks. Many say Donald Trump committed treason by openly calling on Russia to release Hillary Clinton’s emails, and who could forget the “lock her up” catcalls when New Jersey Gov. Chris Christie used his prosecutor skills to eviscerate Mrs. Clinton at the Republican National Convention last week.

Today the DNC breach and doxing took a new turn: the Democratic Congressional Campaign Commitee confirmed it is working with the FBI and CrowdStrike to investigate a breach of its systems it says is "similar" to the DNC hack.

The good news with these high-profile hacks is that cybersecurity is getting attention front and center.

The buzz around tech and politics hasn’t been this intense since the 1990s when Wired Magazine proclaimed “information yearns to be free” and the Netscape IPO gave rise to the boom to bust feeding frenzy that defined the rise of the World Wide Web.

But this feels different. Think 1957 and the Sputnik launch by the former Soviet Union. We may look at the Target breach of December 2013 as something akin to that, at least in terms of cybersecurity. It almost seems as if the rules of the road are shaping up for a new Cold War – a continuous cyber war on our businesses and government agencies that will last even longer than the war on terror.

Cyber experts tell Dark Reading that the malware strains various security groups have tested are consistent with what Russian-sponsored groups have used in the past. The Russians and other nation-states are more aggressive than ever because there is no downside to engaging in destructive hacks.

“There’s very little blowback when these events happen,” says Christopher Porter, manager of the Horizons team at FireEye. “Cybercrime is so prevalent today that it’s really easy for Russia or other nation-states to blame a hack on some random cyber criminal. If institutions were not so regularly hacked, then Russia wouldn’t be able to get away with it as easily. It’s actually easy for them to do these hacks and spread doubt.”

Porter says until the US and the rest of the world take cybersecurity and cybercrime as seriously as they would a physical terrorist attack, the situation could likely continue.

Here's a rundown of what we know about the DNC breach at this point, with additional analysis from key experts.

 

Steve Zurier has more than 30 years of journalism and publishing experience, most of the last 24 of which were spent covering networking and security technology. Steve is based in Columbia, Md. View Full Bio

Previous
1 of 6
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
NicoleM459
50%
50%
NicoleM459,
User Rank: Apprentice
8/2/2016 | 12:12:36 PM
Re: Was Snowden acting as an accomplice?
Wow, is this whole site so politically biased?  I thought this was an InfoSec site?
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
8/1/2016 | 7:27:49 AM
Re: Was Snowden acting as an accomplice?
There's also been the Twitter debate Snowden has engaged in about the ethical implications/improprieties of such leaking, so there's that (although, to stoke the conspiracy-theorist fires, purely for sake of argument, if I wanted to cover up my involvement in such a thing, public statements denouncing it would be one way to go).

Plus, while Snowden may be no Trump fan, I can't imagine he has positive feelings towards Clinton.

But either way, sure, why should he get involved?  Doesn't make sense. 
Faye___Kane
50%
50%
Faye___Kane,
User Rank: Strategist
7/30/2016 | 6:20:46 PM
Re: Was Snowden acting as an accomplice?
 

No, Snowden didn't have anything to do with it.
  • He's not a hacker in any way. He was an NSA network admin who walked out with documents because he has real ethics.
  • Snowden loves America. He was in the military and was a guard for the NSA building at my Alma Mater. His concern for this country is why he blew the whistle on the spooks.
  • Trump is the kind of man Snowden detests.
  • Like China, Russia already has its own army of hackers.

The suspicion that Snowden was behind this is insu;ting and exactly the kind of simpleminded, crazy paranoia that induces the stupid people to vote for Trump.
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
7/30/2016 | 7:34:37 AM
Re: Was Snowden acting as an accomplice?
I tend to doubt this.  The man's got enough going on that he doesn't need to be causing additional trouble.

Unless, of course, part of his asylum agreement includes assisting in this way (which I tend to doubt).

Too conspiracy-theory for my tastes.
Charlie Babcock
50%
50%
Charlie Babcock,
User Rank: Ninja
7/29/2016 | 7:07:48 PM
Was Snowden acting as an accomplice?
Regardless of whether it was the Russian state or merely Russian rogues, if the DNC break-in proves to be of Russian origin, it puts Edward Snowden in the position of publishing confidential information obtained not by him but from a Russian source. I've tended to view his actions as having enough public good to fall short of the treason charge. I hope not to learn that he's taken info. from the Russian government and published it on Wikileaks at a time of the source's choosing. It's the timing element right before the DNC that makes the leak so suspicious and a possible case of meddling in our internal affairs. In which case, Snowden had better negotiate a lifetime lease of his Russian apartment.
RIP, 'IT Security'
Kevin Kurzawa, Senior Information Security Auditor,  11/13/2018
Empathy: The Next Killer App for Cybersecurity?
Shay Colson, CISSP, Senior Manager, CyberClarity360,  11/13/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: I spy, you spy, we all spy...a spy...
Current Issue
Flash Poll
Online Malware and Threats: A Profile of Today's Security Posture
Online Malware and Threats: A Profile of Today's Security Posture
This report offers insight on how security professionals plan to invest in cybersecurity, and how they are prioritizing their resources. Find out what your peers have planned today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-19367
PUBLISHED: 2018-11-20
Portainer through 1.19.2 provides an API endpoint (/api/users/admin/check) to verify that the admin user is already created. This API endpoint will return 404 if admin was not created and 204 if it was already created. Attackers can set an admin password in the 404 case.
CVE-2018-19335
PUBLISHED: 2018-11-20
Google Monorail before 2018-06-07 has a Cross-Site Search (XS-Search) vulnerability because CSV downloads are affected by CSRF, and calculations of download times (for requests with a crafted groupby value) can be used to obtain sensitive information about the content of bug reports.
CVE-2018-19334
PUBLISHED: 2018-11-20
Google Monorail before 2018-05-04 has a Cross-Site Search (XS-Search) vulnerability because CSV downloads are affected by CSRF, and calculations of download times (for requests with an unsupported axis) can be used to obtain sensitive information about the content of bug reports.
CVE-2018-10099
PUBLISHED: 2018-11-20
Google Monorail before 2018-04-04 has a Cross-Site Search (XS-Search) vulnerability because CSV downloads are affected by CSRF, and calculations of download times (for requests with duplicated columns) can be used to obtain sensitive information about the content of bug reports.
CVE-2018-17906
PUBLISHED: 2018-11-19
Philips iSite and IntelliSpace PACS, iSite PACS, all versions, and IntelliSpace PACS, all versions. Default credentials and no authentication within third party software may allow an attacker to compromise a component of the system.