Vulnerabilities / Threats

6/2/2018
09:00 AM
Steve Zurier
Steve Zurier
Slideshows
Connect Directly
Twitter
RSS
E-Mail
50%
50%

5 Tips for Protecting SOHO Routers Against the VPNFilter Malware

Most home office users need to simply power cycle their routers and disable remote access; enterprises with work-at-home employees should move NAS behind the firewall.
Previous
1 of 6
Next

Image Source: Shutterstock via NokkieVector

Image Source: Shutterstock via NokkieVector

News of how the Russians are alleged to have infected more than 500,000 home routers worldwide via the VPNFilter malware broke last week, leaving home users and security managers scratching their heads about how to best to lock themselves down.

Craig Williams, director of Talos outreach, a leading member of the Cisco Talos research team that discovered the malware, says most SOHO users simply need to reboot their routers and do a firmware upgrade.

“The good news based on our research is that VPNFilter used common hacking techniques on common vulnerabilities,” Williams says. “This was not a zero-day attack.

According to a recent Symantec blog post, VPNFilter is a three-stage malware.

Stage 1 gets installed first and is used to maintain a persistent presence on the infected device; it will contact a command and control server to download further modules.

Stage 2 contains the main payload and does file collection, command execution, data exfiltration and device management. It also has a destructive capability and can effectively "brick" the device if it receives a command from the attackers. It does this by overwriting a section of the device’s firmware and rebooting, rendering it unusable.

Stage 3 contains several known modules, which act as plugins for Stage 2. These include a packet sniffer for spying on traffic that’s routed through the device, with the capability for stealing website credentials and monitoring Modbus SCADA protocols. Another Stage 3 module lets Stage 2 communicate using Tor. Symantec says rebooting the device will clear out Stage 2 or 3 elements. However, if the device becomes infected, the continuing presence of Stage 1 means that Stage 2 and Stage 3 can be relaunched.

Vikram Thakur, technical director at Symantec, says that’s why the FBI took over the "toknowallall.com" domain. By sinkholing the domain, any further attacks get sent to FBI servers, which can intercept the malware. Thakur also agrees with Williams that first and foremost, people should power cycle their routers and do the firmware updates.

"The FBI sees this as a teachable moment, so it’s trying to get the word out that people should reboot their routers and set up regular routines for doing firmware upgrades," he says, adding that the federal government expects that it will take a year or two for people to change their security habits when it comes to protecting home routers.  

Here are additional insights from Williams and Thakur for SOHO users and security managers to defend against the VPNFilter malware.

 

Steve Zurier has more than 30 years of journalism and publishing experience, most of the last 24 of which were spent covering networking and security technology. Steve is based in Columbia, Md. View Full Bio

Previous
1 of 6
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
joe9804
50%
50%
joe9804,
User Rank: Apprentice
6/7/2018 | 6:00:39 PM
Thanks giving
Thanks for giving information about the malware. Many blogs have written about the virus but nobody gives the tips that how to prevent this malware. Buti am a Netgear router user. when heard about this malware,icontact 
<a href="https://netgears.support/netgear-router-support-usa/">netgear router support usa</a>

 and they told me that my router was not infected with that virus. So if any Netgear user's router infected with that malware then they should contact them for support.
baranteo
50%
50%
baranteo,
User Rank: Apprentice
6/4/2018 | 6:16:58 AM
new
great interview. Useful and informative
Meet 'Bro': The Best-Kept Secret of Network Security
Greg Bell, CEO, Corelight,  6/14/2018
Containerized Apps: An 8-Point Security Checklist
Jai Vijayan, Freelance writer,  6/14/2018
Four Faces of Fraud: Identity, 'Fake' Identity, Ransomware & Digital
David Shefter, Chief Technology Officer at Ziften Technologies,  6/14/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-0291
PUBLISHED: 2018-06-20
A vulnerability in the Simple Network Management Protocol (SNMP) input packet processor of Cisco NX-OS Software could allow an authenticated, remote attacker to cause the SNMP application on an affected device to restart unexpectedly. The vulnerability is due to improper validation of SNMP protocol ...
CVE-2018-0292
PUBLISHED: 2018-06-20
A vulnerability in the Internet Group Management Protocol (IGMP) Snooping feature of Cisco NX-OS Software could allow an unauthenticated, adjacent attacker to execute arbitrary code and gain full control of an affected system. The attacker could also cause an affected system to reload, resulting in ...
CVE-2018-0293
PUBLISHED: 2018-06-20
A vulnerability in role-based access control (RBAC) for Cisco NX-OS Software could allow an authenticated, remote attacker to execute CLI commands that should be restricted for a nonadministrative user. The attacker would have to possess valid user credentials for the device. The vulnerability is du...
CVE-2018-0294
PUBLISHED: 2018-06-20
A vulnerability in the write-erase feature of Cisco FXOS Software and Cisco NX-OS Software could allow an authenticated, local attacker to configure an unauthorized administrator account for an affected device. The vulnerability exists because the affected software does not properly delete sensitive...
CVE-2018-0295
PUBLISHED: 2018-06-20
A vulnerability in the Border Gateway Protocol (BGP) implementation of Cisco NX-OS Software could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition due to the device unexpectedly reloading. The vulnerability is due to incomplete input validation of the BGP update...