Threat Intelligence

5/29/2018
02:15 PM
50%
50%

FBI Warns Users to Reboot All SOHO Routers

Everyone with a home router should reboot their systems as a precaution in the wake of the recently discovered VPNFilter attack infrastructure.

The FBI is widening its guidance on who should reboot a SOHO router in response to the VPNFilter attack that infected more than a half million routers and network-attached storage devices. The new list? Everyone.

The original notices of the attack listed routers and instructed everyone with an affected router to reboot. Now, the FBI has broadened its instructions, directing everyone who owns a SOHO router to reboot now.

The FBI is calling for the reboot even though the agency acknowledges that the first-stage loader for the botnet is persistent, remaining in place through resets and reboots.

According to the Justice Department, the hacking collective known as APT28, or FancyBear, is responsible for the attack. The collective, considered a state-sponsored cybercriminal organization, is known as the group that played heavily in efforts to disrupt the 2016 US elections.

For more, read 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
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
5/31/2018 | 3:37:45 PM
Re: SOHO Only?
Many SOHO's have also already released patches for the exploit. The reboot will allow those patches to be applied. But you are definitely correct, you would be hard pressed to see Commercial grade networking gear and SOHO's sharing the same threat landscape.
Norman.Neil
50%
50%
Norman.Neil,
User Rank: Apprentice
5/31/2018 | 8:43:32 AM
Re: SOHO Only?
SOHO = small office, home office

It is meant to include all consumer-grade routers.

Commercial-grade routers (i.e. CISCO, HP, etc.) generally have much stronger security associated with their operation, like requiring administrative privileges to install anything on them.   
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
5/30/2018 | 6:24:39 PM
SOHO Only?
Is this only about this router, what about others?
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
5/30/2018 | 6:23:53 PM
Re: The FBI is widening its guidance
rather than just more "Russia! Russia! Russia!" in order to distract domestic attention Good point, never thought in that way.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
5/30/2018 | 6:23:05 PM
Re: The FBI is widening its guidance
Perhaps the concentrated volume of reestablishing connections with the botnet ... Or giverment know something and they do not let us know.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
5/30/2018 | 6:21:46 PM
Re: The FBI is widening its guidance
Hard to see the rationale behind call for reboot of all SOHO routers I am also not sure about the real objective of this action.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
5/30/2018 | 6:20:24 PM
Reboot?
Wondering how reboot would remove the flow, how did happen in the first place?
BrianN060
50%
50%
BrianN060,
User Rank: Ninja
5/30/2018 | 3:48:48 PM
The FBI is widening its guidance
Hard to see the rationale behind call for reboot of all SOHO routers (given ...that the first-stage loader for the botnet is persistent...).  Perhaps the concentrated volume of reestablishing connections with the botnet command/control will be useful, at least as an indication of scope and scale.  Hope it's something like that, rather than just more "Russia! Russia! Russia!" in order to distract domestic attention away from other issues and concerns. 
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
Why CISOs Need a Security Reality Check
Joel Fulton, Chief Information Security Officer for Splunk,  6/13/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-12557
PUBLISHED: 2018-06-19
An issue was discovered in Zuul 3.x before 3.1.0. If nodes become offline during the build, the no_log attribute of a task is ignored. If the unreachable error occurred in a task used with a loop variable (e.g., with_items), the contents of the loop items would be printed in the console. This could ...
CVE-2018-12559
PUBLISHED: 2018-06-19
An issue was discovered in the cantata-mounter D-Bus service in Cantata through 2.3.1. The mount target path check in mounter.cpp `mpOk()` is insufficient. A regular user can consequently mount a CIFS filesystem anywhere (e.g., outside of the /home directory tree) by passing directory traversal sequ...
CVE-2018-12560
PUBLISHED: 2018-06-19
An issue was discovered in the cantata-mounter D-Bus service in Cantata through 2.3.1. Arbitrary unmounts can be performed by regular users via directory traversal sequences such as a home/../sys/kernel substring.
CVE-2018-12561
PUBLISHED: 2018-06-19
An issue was discovered in the cantata-mounter D-Bus service in Cantata through 2.3.1. A regular user can inject additional mount options such as file_mode= by manipulating (for example) the domain parameter of the samba URL.
CVE-2018-12562
PUBLISHED: 2018-06-19
An issue was discovered in the cantata-mounter D-Bus service in Cantata through 2.3.1. The wrapper script 'mount.cifs.wrapper' uses the shell to forward the arguments to the actual mount.cifs binary. The shell evaluates wildcards (such as in an injected string:/home/../tmp/* string).