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.

IoT
6/26/2019
05:30 PM
50%
50%

New Linux Worm Attacks IoT Devices

Silex has 'bricked' more than 2,000 Linux-based IoT devices so far.

A new Internet of Things (IoT) bricking worm — malware designed to permanently disable the hardware it infects — is hitting Linux-based devices, and it appears the culprit responsible for the attack is 14 years old. 

The new software, dubbed "Silex," is running across the Internet looking for Linux systems deployed with default admin credentials. Once it finds such a system, it overwrites all of the system's storage with random data, drops its firewall rules, removes its network configuration, and then restarts the system — effectively rendering the device useless.

Discovered by Larry Cashdollar, a vulnerability researcher and member of Akamai's Security Incident Response Team, the software is purely destructive; it captures no data and asks for no ransom. Researcher Ankit Anubhav traced the malware back to its origins and found the developer, who uses the online name "Light Leafon." According to Anubhav, the malware's author says that additional destructive capabilities are planned for future Silex variants.

More than 2,000 systems have already been damaged by Silex, which is not technically limited to IoT devices. It could attack any Linux system deployed on the Internet with open telnet ports and default admin credentials. Other researchers have noted that the command-and-control servers for Silex have IP addresses linked to Iran, leading some to speculate that political, as well as simply destructive, aims are behind its release.

Read more herehere, and 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
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Page 1 / 2   >   >>
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
6/30/2019 | 9:02:42 AM
Re: Defaults
That's depressing.
tdsan
50%
50%
tdsan,
User Rank: Ninja
6/29/2019 | 8:34:21 PM
Re: Defaults
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
6/29/2019 | 8:16:53 PM
Re: Defaults
Definitely concur here. But obviously there are still those out there who are foolish enough for this to still be effective. :( Its quite sad.
tdsan
50%
50%
tdsan,
User Rank: Ninja
6/28/2019 | 8:46:28 PM
Re: For fun
"the software is purely destructive; it captures no data and asks for no ransom. Researcher Ankit Anubhav traced the malware back to its origins and found the developer, who uses the online name "Light Leafon." " Obviously this was for fun. Distraction is huge.

I am not so sure it was all for fun, I think it was also being used to test its capability for another purpose. Think about this, if the actor could access systems with default passwords, then what about writing a hash algorithm to run a for loop to check for possible password combinations.
  1. Check to see if they can get to the device and apply a default username and password
  2. Create a payload or add a function statement that goes through a list of passwords

I think this is a logical step in their next attempt but again we are theorizing, only time will tell.
import getpass
import sys
import telnetlib
import time

#Getting the user information
user=input("Enter User name: ")
password=getpass.getpass()

#open file
iplist=open("ipfile.txt")

#Loop through IP address and execute commands
for line in  iplist:

 Host=line.strip("\n")    
 print ("Configuring Switch",Host)
 tn = telnetlib.Telnet(Host)    
 tn.read_until(b"Username: ")   
 tn.write(user.encode('ascii') + b"\n")
 tn.read_until(b"Password: ")
 tn.write(password.encode('ascii')+b"\n")
 time.sleep(2)     
 tn.write(b"enable\n")  
 time.sleep(2)
 tn.write(b"admin\n")  
 time.sleep(2)
 tn.write(b"config t\n")
 time.sleep(2)
 tn.write(b"snmp-server community Secured ro\n") 
 print ("Switch ",Host,"Configured")
 line=tn.read_some()
 tn.close()                           
 print (line)                      

#closing file 
ipfile.close()

 Todd
tdsan
50%
50%
tdsan,
User Rank: Ninja
6/28/2019 | 7:40:48 PM
Re: Linux Worm Exploits and Defenses
Yes, I agree, that is why I had mentioned in my excert that the vendor should disable telnet altogether or block it.

In addition, companies like Cisco and Juniper ask the user to change the default password. If the user does not change the password then the system should be halted until they change it based on recommended security guidelines (listed below).

NIST password guidelines - "NIST guidance recommends the following for passwords: An eight character minimum and 64 character maximum length. The ability to use all special characters but no special requirement to use them."
  • An eight character minimum and 64 character maximum length
  • The ability to use all special characters but no special requirement to use them
  • Restrict sequential and repetitive characters (e.g. 12345 or aaaaaa)
  • Restrict context specific passwords (e.g. the name of the site, etc.)
  • Restrict commonly used passwords (e.g. [email protected], etc.)
  • Restrict passwords obtained from previous breach corpuses
NIST Security Password Guidelines

Todd

 
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/28/2019 | 6:47:51 PM
Defaults
It could attack any Linux system deployed on the Internet with open telnet ports and default admin credentials. So it is not supposed to be an attack at all. Who would leave defaults as they are today?
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/28/2019 | 6:46:12 PM
Re: Linux Worm Exploits and Defenses
The IoT devices related to the internet. That is why they become vulnerable too.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/28/2019 | 6:44:13 PM
Re: Linux Worm Exploits and Defenses
A number of companies are doing this but after reading the report, it seems this practice is not performed across the board. Most SME would not pay enough attention to it so they mostly miss it.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/28/2019 | 6:42:14 PM
Re: Linux Worm Exploits and Defenses
I do agree the responsibility should rest with the consumer where the system asks or provides insight on how to change the admin password Anting left to consumers will be at high risk. Better to avoid expecting anything from consumers.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/28/2019 | 6:40:46 PM
For fun
the software is purely destructive; it captures no data and asks for no ransom. Researcher Ankit Anubhav traced the malware back to its origins and found the developer, who uses the online name "Light Leafon." Obviously this was for fun. Distraction is huge.
Page 1 / 2   >   >>
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/6/2020
Ripple20 Threatens Increasingly Connected Medical Devices
Kelly Sheridan, Staff Editor, Dark Reading,  6/30/2020
DDoS Attacks Jump 542% from Q4 2019 to Q1 2020
Dark Reading Staff 6/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
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-15505
PUBLISHED: 2020-07-07
MobileIron Core and Connector before 10.3.0.4, 10.4.x before 10.4.0.4, 10.5.x before 10.5.1.1, 10.5.2.x before 10.5.2.1, and 10.6.x before 10.6.0.1, and Sentry before 9.7.3 and 9.8.x before 9.8.1, allow remote attackers to execute arbitrary code via unspecified vectors.
CVE-2020-15506
PUBLISHED: 2020-07-07
MobileIron Core and Connector before 10.3.0.4, 10.4.x before 10.4.0.4, 10.5.x before 10.5.1.1, 10.5.2.x before 10.5.2.1, and 10.6.x before 10.6.0.1 allow remote attackers to bypass authentication mechanisms via unspecified vectors.
CVE-2020-15507
PUBLISHED: 2020-07-07
MobileIron Core and Connector before 10.3.0.4, 10.4.x before 10.4.0.4, 10.5.x before 10.5.1.1, 10.5.2.x before 10.5.2.1, and 10.6.x before 10.6.0.1 allow remote attackers to read files on the system via unspecified vectors.
CVE-2020-15096
PUBLISHED: 2020-07-07
In Electron before versions 6.1.1, 7.2.4, 8.2.4, and 9.0.0-beta21, there is a context isolation bypass, meaning that code running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions. Apps using "contextIsolation" are affecte...
CVE-2020-4075
PUBLISHED: 2020-07-07
In Electron before versions 7.2.4, 8.2.4, and 9.0.0-beta21, arbitrary local file read is possible by defining unsafe window options on a child window opened via window.open. As a workaround, ensure you are calling `event.preventDefault()` on all new-window events where the `url` or `options` is not ...