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
Oldest First  |  Newest First  |  Threaded View
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?
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.

 
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?


COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/22/2020
The Problem with Artificial Intelligence in Security
Dr. Leila Powell, Lead Security Data Scientist, Panaseer,  5/26/2020
How an Industry Consortium Can Reinvent Security Solution Testing
Henry Harrison, Co-founder & Chief Technology Officer, Garrison,  5/21/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
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
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-10737
PUBLISHED: 2020-05-27
A race condition was found in the mkhomedir tool shipped with the oddjob package in versions before 0.34.5 and 0.34.6 wherein, during the home creation, mkhomedir copies the /etc/skel directory into the newly created home and changes its ownership to the home's user without properly checking the hom...
CVE-2020-13622
PUBLISHED: 2020-05-27
JerryScript 2.2.0 allows attackers to cause a denial of service (assertion failure) because a property key query for a Proxy object returns unintended data.
CVE-2020-13623
PUBLISHED: 2020-05-27
JerryScript 2.2.0 allows attackers to cause a denial of service (stack consumption) via a proxy operation.
CVE-2020-13616
PUBLISHED: 2020-05-26
The boost ASIO wrapper in net/asio.cpp in Pichi before 1.3.0 lacks TLS hostname verification.
CVE-2020-13614
PUBLISHED: 2020-05-26
An issue was discovered in ssl.c in Axel before 2.17.8. The TLS implementation lacks hostname verification.