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.

Comments
Home Routers Being Targeted in DNS Hijacking Attack, Trend Micro Says
Newest First  |  Oldest First  |  Threaded View
nickhudson
50%
50%
nickhudson,
User Rank: Apprentice
10/12/2017 | 8:25:52 AM
What is DNS Hijacking really? And how do we protect?
How do we protect ourselves from the attacks that happened at ISP servers? There are different attacks that happens including spoofing and poisoning. How do someone knows which type of attack has occured?
GlennF622
100%
0%
GlennF622,
User Rank: Apprentice
5/30/2015 | 1:32:51 AM
Re: Is there a defense for installed routers?
There are several things you can do. The first is do a DNS leak test: www (dot) dnsleaktest.com to see if your DNS has been changed or leaking.

I would recommend using an alternate DNS than your ISP's such as OpenDNS so you have built in phishing, botnet, and rogue website protection. You can sign up for a free account to get even more content filtering by category. You change this in your router so everything connected to it gets this protection.

Change your router default password

Check for firmware updates in your router

Use WPA2 encryption on your WIFI and use a random character password. Don't use words as this can be cracked

Go to www (dot) routercheck.com and download the free app for android devices that automatically check for some well known router vulnerabilities on your router.

 
Charlie Babcock
50%
50%
Charlie Babcock,
User Rank: Ninja
5/29/2015 | 7:50:55 PM
Is there a defense for installed routers?
This is an especially nefarious hazard. People sitting in the security of their own homes and doing health care communications or banking transactions aren't thinking about how their router might have been targeted. Is there an effective defense that can be added to home routers with an existing and perhaps outdated copy of DNS? How can you tell if your router has been infected?


News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-24285
PUBLISHED: 2021-04-12
INTELBRAS TELEFONE IP TIP200 version 60.61.75.22 allows an attacker to obtain sensitive information through /cgi-bin/cgiServer.exx.
CVE-2021-29379
PUBLISHED: 2021-04-12
** UNSUPPORTED WHEN ASSIGNED ** An issue was discovered on D-Link DIR-802 A1 devices through 1.00b05. Universal Plug and Play (UPnP) is enabled by default on port 1900. An attacker can perform command injection by injecting a payload into the Search Target (ST) field of the SSDP M-SEARCH discover pa...
CVE-2015-20001
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
CVE-2020-36317
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
CVE-2020-36318
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.