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.

Attacks/Breaches

8/14/2014
04:45 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Stuxnet Exploits Still Alive & Well

Exploits continue abusing a four-year-old bug used in the Stuxnet attack, Kaspersky Lab says.

One of the main vulnerabilities used in the infamous Stuxnet attack -- patched four years ago -- is being used in attack attempts against millions of machines around the world, according to new data.

Kaspersky Lab found that during November 2013 and June 2014, the Windows Shell flaw (CVE-2010-2568) used by Stuxnet to gain administrative rights on a Windows machine remotely was detected 50 million times attacking some 19 million machines in Vietnam (42.45%), India (11.7%), Indonesia (9.43%), Brazil (5.52%), and Algeria (3.74%).

Those nations also have some of the most Windows XP installations, which likely explains why a high percentage of them are the target of that Stuxnet vulnerability, according to Kaspersky Lab. Some 64.19% of those machines in the sample were XP; 27.99%, Windows 7; 3.99%, Windows Server 2008; and 1.58%, Windows Server 2003. Around 4.52% of all active XP machines are in the US, according to Kaspersky's data.

The "critical" Windows Shell flaw would let a remote or local attacker run code via a malicious .LNK or .PIF file via an improperly handled icon displayed in Windows Explorer. Microsoft issued a patch for the vulnerability on August 2, 2010; Stuxnet was first discovered in June of that year.

Kaspersky Lab researchers say the problem likely has to do with servers that aren't being updated or that lack proper security software. The servers also could be infested by a worm that exploits the flaw and spreads the infection.

"We have seen some vulnerabilities go back to 2009-2010, and I suspect that we can find even older examples. Therefore I am not surprised by a 2010 CVE that Stuxnet is using, is still viable," says Barry Sheitman, director of security strategy at Imperva.

The problem, of course, is that many black hat hackers know that old vulns die hard, so they abuse them, he says.

The full Kaspersky Lab Stuxnet report is available here.

Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
securityaffairs
50%
50%
securityaffairs,
User Rank: Ninja
8/18/2014 | 1:25:44 PM
as expected
We must consider as primary causes the following:
  • Militarization of the cyberspace as as side effect diffusion for a long time of exploits used in the "cyber weapons"
  • Presence on the Internet for a great number of servers that aren't updated or that lack proper defensive solutions. 

No doubts that in the future a growing number of similar cases will be discovered

 

 
Kelly Jackson Higgins
50%
50%
Kelly Jackson Higgins,
User Rank: Strategist
8/18/2014 | 8:59:15 AM
Re: Four years old
It's mostly in nations with late-technology adoption and a lot of XP still hanging around. So that really old vulns are still exploitable in those regions is not really surprising.
Bprince
50%
50%
Bprince,
User Rank: Ninja
8/15/2014 | 8:44:18 PM
Four years old
A four-year old vulnerability? I mean honestly that's pretty negligent to me, especially if any of these are corporate machines. 

BP
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/13/2020
Omdia Research Launches Page on Dark Reading
Tim Wilson, Editor in Chief, Dark Reading 7/9/2020
Russian Cyber Gang 'Cosmic Lynx' Focuses on Email Fraud
Kelly Sheridan, Staff Editor, Dark Reading,  7/7/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-10987
PUBLISHED: 2020-07-13
The goform/setUsbUnload endpoint of Tenda AC15 AC1900 version 15.03.05.19 allows remote attackers to execute arbitrary system commands via the deviceName POST parameter.
CVE-2020-10988
PUBLISHED: 2020-07-13
A hard-coded telnet credential in the tenda_login binary of Tenda AC15 AC1900 version 15.03.05.19 allows unauthenticated remote attackers to start a telnetd service on the device.
CVE-2020-10989
PUBLISHED: 2020-07-13
An XSS issue in the /goform/WifiBasicSet endpoint of Tenda AC15 AC1900 version 15.03.05.19 allows remote attackers to execute malicious payloads via the WifiName POST parameter.
CVE-2020-10986
PUBLISHED: 2020-07-13
A CSRF issue in the /goform/SysToolReboot endpoint of Tenda AC15 AC1900 version 15.03.05.19 allows remote attackers to reboot the device and cause denial of service via a payload hosted by an attacker-controlled web page.
CVE-2019-19338
PUBLISHED: 2020-07-13
A flaw was found in the fix for CVE-2019-11135, in the Linux upstream kernel versions before 5.5 where, the way Intel CPUs handle speculative execution of instructions when a TSX Asynchronous Abort (TAA) error occurs. When a guest is running on a host CPU affected by the TAA flaw (TAA_NO=0), but is ...