Comments
Jailed Hacker Claims Proof He Breached DNC on Russia's Orders
Newest First  |  Oldest First  |  Threaded View
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
1/4/2018 | 8:34:31 AM
Re: And if the DNC had allowed real investigators...
Best comeback ever.  
SchemaCzar
50%
50%
SchemaCzar,
User Rank: Strategist
1/3/2018 | 3:48:43 PM
Re: And if the DNC had allowed real investigators...
You just forced me to have sympathy on hackers...
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
1/3/2018 | 1:15:10 PM
Re: And if the DNC had allowed real investigators...
I cannot help but get a chuckle out of this one --- what if all the Russians managed to gain access to were text files of Anthony Weiner's sexting chats????
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
12/31/2017 | 9:59:21 PM
Re: Not Surprising
Russian and Eastern European hackers have a long history of having an "understanding" with government officials -- having their consent to turn a blind eye if not their direct blessing, so long as they keep their activities away from fellow citizens. That's at the very least.

In other cases, it has been known in the intelligence community that Russian government officials outright work with independent black hats (as with other governments). I suspect that this proof, if it turns out to be actual proof, will get a lot of attention in the public, but in terms of actual policy will not mean a heck of a lot because it's old news to the people whose job it is to do things about it.
SchemaCzar
100%
0%
SchemaCzar,
User Rank: Strategist
12/29/2017 | 11:02:23 AM
And if the DNC had allowed real investigators...
DNC's hiring of CrowdStrike and refusal to allow FBI digital forensics to investigate makes this impossible to pursue.  The dishonesty of claiming Russian hacking and its damage to US democracy while not bringing it to Federal investigation now leaves us blind in dealing with Kozlovsky and his allegations.  For me - I don't believe the claims.  The FSB has plenty of its own resources and an ability to cover its tracks that makes using an outsider completely unnecessary, and risky.  A free-wheeling, free-travelling robber like Koslovsky is even worse.  Perhaps Koslovsky believes he was engaged by the FSB - as if he cared who paid him - but I don't.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
12/29/2017 | 7:32:42 AM
Not Surprising
This isn't surprising in the least that this could have been performed with the backing of a nation-state. The question is, definitely proving this to be the case what would be the recourse?


White House Cybersecurity Strategy at a Crossroads
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/17/2018
Lessons from My Strange Journey into InfoSec
Lysa Myers, Security Researcher, ESET,  7/12/2018
What's Cooking With Caleb Sima
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/12/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14339
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the MMSE dissector could go into an infinite loop. This was addressed in epan/proto.c by adding offset and length validation.
CVE-2018-14340
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, dissectors that support zlib decompression could crash. This was addressed in epan/tvbuff_zlib.c by rejecting negative lengths to avoid a buffer over-read.
CVE-2018-14341
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the DICOM dissector could go into a large or infinite loop. This was addressed in epan/dissectors/packet-dcm.c by preventing an offset overflow.
CVE-2018-14342
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the BGP protocol dissector could go into a large loop. This was addressed in epan/dissectors/packet-bgp.c by validating Path Attribute lengths.
CVE-2018-14343
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the ASN.1 BER dissector could crash. This was addressed in epan/dissectors/packet-ber.c by ensuring that length values do not exceed the maximum signed integer.