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
johnsmith247
50%
50%
johnsmith247,
User Rank: Apprentice
10/31/2018 | 4:12:51 AM
Re: The FBI is widening its guidance
I read some news before some days ago, According to the FBI warning, "the malware targets IP Address Conflict  routers produced by several manufacturers and network-attached storage devices by at least one manufacturer." 
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. 
Devastating Cyberattack on Email Provider Destroys 18 Years of Data
Jai Vijayan, Freelance writer,  2/12/2019
Up to 100,000 Reported Affected in Landmark White Data Breach
Kelly Sheridan, Staff Editor, Dark Reading,  2/12/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-8358
PUBLISHED: 2019-02-16
In Hiawatha before 10.8.4, a remote attacker is able to do directory traversal if AllowDotFiles is enabled.
CVE-2019-8354
PUBLISHED: 2019-02-15
An issue was discovered in SoX 14.4.2. lsx_make_lpf in effect_i_dsp.c has an integer overflow on the result of multiplication fed into malloc. When the buffer is allocated, it is smaller than expected, leading to a heap-based buffer overflow.
CVE-2019-8355
PUBLISHED: 2019-02-15
An issue was discovered in SoX 14.4.2. In xmalloc.h, there is an integer overflow on the result of multiplication fed into the lsx_valloc macro that wraps malloc. When the buffer is allocated, it is smaller than expected, leading to a heap-based buffer overflow in channels_start in remix.c.
CVE-2019-8356
PUBLISHED: 2019-02-15
An issue was discovered in SoX 14.4.2. One of the arguments to bitrv2 in fft4g.c is not guarded, such that it can lead to write access outside of the statically declared array, aka a stack-based buffer overflow.
CVE-2019-8357
PUBLISHED: 2019-02-15
An issue was discovered in SoX 14.4.2. lsx_make_lpf in effect_i_dsp.c allows a NULL pointer dereference.