News

2/16/2017
09:40 AM
50%
50%

Ukraine Blames Russia For New Virus Targeting Infrastructure

The Russian security service, software firms, and criminal hackers are accused of orchestrating cyberattacks on Ukraine's infrastructure.

Ukraine has accused the Russian security service of attacking the country's infrastructure using a new virus designed to render industrial equipment non-functional, Reuters reports. At a recent press conference, Ukraine's security service chief of staff Oleksandr Tkachuk stated the attacks appear to come from the creators of malware BlackEnergy; the same people were allegedly responsible for cyberattacks on the country's energy industry since December 2015.

Ukraine blamed Russia for 6,500 cyberattacks in November and December of last year, including those on Kiev's power grid and the State Treasury. If the most recent allegations are true, Ukraine could push the US for a joint effort in fighting the Russian cyberthreat.

"Russian hackers and infobots become an important tool of the aggression against our country," said Tkachuk, adding that a mechanism called Telebots was employed to target computers controlling its industrial infrastructure.

Another cybersecurity company, CyberX, claims to have unearthed an espionage scheme in Ukraine targeting 60 victims. It fears this could be a launching pad for further attacks.

Read full story here.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Crypt0L0cker
50%
50%
Crypt0L0cker,
User Rank: Strategist
2/16/2017 | 11:15:38 AM
Re: Ukraine Blames Russia For New Virus Targeting Infrastructure
Nothing new for me here. They (Russians) became a threat for all modern society and will attack everybody who looks weaker or just unaware. This country follows a criminal psychology and behave just like a criminal. They can respect only another power and try to avoid punishment.
6 Ways Greed Has a Negative Effect on Cybersecurity
Joshua Goldfarb, Co-founder & Chief Product Officer, IDRRA ,  6/11/2018
Weaponizing IPv6 to Bypass IPv4 Security
John Anderson, Principal Security Consultant, Trustwave Spiderlabs,  6/12/2018
'Shift Left' & the Connected Car
Rohit Sethi, COO of Security Compass,  6/12/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-12026
PUBLISHED: 2018-06-17
During the spawning of a malicious Passenger-managed application, SpawningKit in Phusion Passenger 5.3.x before 5.3.2 allows such applications to replace key files or directories in the spawning communication directory with symlinks. This then could result in arbitrary reads and writes, which in tur...
CVE-2018-12027
PUBLISHED: 2018-06-17
An Insecure Permissions vulnerability in SpawningKit in Phusion Passenger 5.3.x before 5.3.2 causes information disclosure in the following situation: given a Passenger-spawned application process that reports that it listens on a certain Unix domain socket, if any of the parent directories of said ...
CVE-2018-12028
PUBLISHED: 2018-06-17
An Incorrect Access Control vulnerability in SpawningKit in Phusion Passenger 5.3.x before 5.3.2 allows a Passenger-managed malicious application, upon spawning a child process, to report an arbitrary different PID back to Passenger's process manager. If the malicious application then generates an e...
CVE-2018-12029
PUBLISHED: 2018-06-17
A race condition in the nginx module in Phusion Passenger 3.x through 5.x before 5.3.2 allows local escalation of privileges when a non-standard passenger_instance_registry_dir with insufficiently strict permissions is configured. Replacing a file with a symlink after the file was created, but befor...
CVE-2018-12071
PUBLISHED: 2018-06-17
A Session Fixation issue exists in CodeIgniter before 3.1.9 because session.use_strict_mode in the Session Library was mishandled.