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.

Database Security
Authentication
Mobile
Privacy
Compliance
Careers and People
Identity & Access Management
Security Monitoring
Advanced Threats
Insider Threats
Vulnerability Management
Comments
After DHS Notice, 21 States Reveal They Were Targeted During Election
Oldest First  |  Newest First  |  Threaded View
Page 1 / 2   >   >>
jenshadus
67%
33%
jenshadus,
 User Rank: Strategist
9/26/2017 | 10:01:00 AM
Really? We're still pointing fingers at the Russians?
There are so many things in this article that I disagree with.  I'll just point out one.

What's the evidence it was the Russians.  I went to Defcon and it took many of these people but 10 to 15 minutes to hack into the sample machines that were available.  I heard that one of them turned the booth into a PACMAN game.  Don't know if that's also true.  Virginia had one 100% red country that voted 100% blue, Maryland is notorious for sending people to vote in Virginia using fake ID's, not counting all the dead people who come in to vote (huh?). 

 
screwbird
50%
50%
screwbird,
 User Rank: Strategist
9/26/2017 | 10:37:43 PM
Re: Really? We're still pointing fingers at the Russians?
It would be nice to know how attribution was established. 
REISEN1955
100%
0%
REISEN1955,
 User Rank: Ninja
9/27/2017 | 9:50:09 AM
Re: Really? We're still pointing fingers at the Russians?
There are any number of fine countries to blame - North Korea and China to start with and just assuming that all BAD in the world belongs to Russian hackers is simplistic.  IP trace does not mean a tinker's damn as those can be hidden, fudged quite easily.    As for me,I personally fear hackers from Towaco, New Jerssy!!!  Now THAT is a tough area!!! LOL
jenshadus
50%
50%
jenshadus,
 User Rank: Strategist
9/27/2017 | 10:42:45 AM
Re: Really? We're still pointing fingers at the Russians?
Amen
Dr.T
100%
0%
Dr.T,
 User Rank: Ninja
9/27/2017 | 11:08:09 AM
DHS is late
It is a little bit late for DHS to come out with this information, everybody knows not only Russians but may other countries try to attack other counties’ systems and that includes election systems too.
Dr.T
100%
0%
Dr.T,
 User Rank: Ninja
9/27/2017 | 11:09:43 AM
Re: Really? We're still pointing fingers at the Russians?
“What's the evidence it was the Russians.” Good question. There may not be a clear set of evidence. However Russians and many others have interests in attacking US systems.
Dr.T
100%
0%
Dr.T,
 User Rank: Ninja
9/27/2017 | 11:11:24 AM
Re: Really? We're still pointing fingers at the Russians?
“Virginia using fake ID's, not counting all the dead people who come in to vote (huh?). “ Yes, fake ID would be another major issue for an selection system. All needs to be avoided,
Dr.T
50%
50%
Dr.T,
 User Rank: Ninja
9/27/2017 | 11:12:37 AM
Re: Really? We're still pointing fingers at the Russians?
“There are any number of fine countries to blame - North Korea and China to start with “ That is true, I would add many others that have capabilities to execute an attack.
Dr.T
50%
50%
Dr.T,
 User Rank: Ninja
9/27/2017 | 11:14:55 AM
Re: Really? We're still pointing fingers at the Russians?
“IP trace does not mean a tinker's damn as those can be hidden, fudged quite easily” I would agree, IP address can easily be spoofed. It is not a traceable entity, there needs to be other mechanisms to track the attackers.
Joe Stanganelli
50%
50%
Joe Stanganelli,
 User Rank: Ninja
9/27/2017 | 7:54:34 PM
Re: Really? We're still pointing fingers at the Russians?
@Dr. T: Absolutely. Reminds me of the forensics tracking that big Sony hack that was traced to North Korea...except other researchers eventually traced it to...Russia!

And even then, that location tracking may not have been accurate/the whole story. There seems to be little shortage of IP-masking tech if you know where to look (no pun intended).
Page 1 / 2   >   >>


News
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-2020-24285
PUBLISHED: 2021-04-12
INTELBRAS TELEFONE IP TIP200 version 60.61.75.22 allows an attacker to obtain sensitive information through /cgi-bin/cgiServer.exx.
CVE-2021-29379
PUBLISHED: 2021-04-12
** UNSUPPORTED WHEN ASSIGNED ** An issue was discovered on D-Link DIR-802 A1 devices through 1.00b05. Universal Plug and Play (UPnP) is enabled by default on port 1900. An attacker can perform command injection by injecting a payload into the Search Target (ST) field of the SSDP M-SEARCH discover pa...
CVE-2015-20001
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
CVE-2020-36317
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
CVE-2020-36318
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.