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.

Network Security

7/15/2019
01:10 PM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

DNS Hijacking on the Rise as Warning Is Issued

The National Cyber Security Centre, a part of the UK's GCHQ, has issued an advisory that deals with Domain Name System (DNS) hijacking by threat actors.

The National Cyber Security Centre, a part of the UK's GCHQ, has issued an advisorythat deals with Domain Name System (DNS) hijacking by threat actors.

DNS hijacking refers to the unauthorized alteration of DNS entries in a zone file on an authoritative DNS server (or the modification of domain configurations in relation to a domain registrar) by an attacker. This can be used to redirect traffic in order to capture sensitive information.

The NCSC has recently observed various attacks which exploit the DNS system at different levels. This includes the "Sea Turtle" bad actors which have been plaguing Brazil. Avast has discovered that 180,000 users in the Avast user base, located in Brazil have had their DNS hijacked in the first half of 2019.

A threat actor using this method can create malicious DNS records. These records can hide a malicious site within an organization's familiar domains. The camouflage can help hide a phishing site, for example.

Domain-validated SSL certificates are issued based on the creation of DNS records; so an attacker may obtain valid SSL certificates for a domain name, which could be used to create a threat website. An attacker could carry out transparent proxying with this method. This is when the attacker modifies an organization's configured domain zone entries (such as "A" or "CNAME" records) to point traffic to their own IP address (which would be infrastructure that they manage).

The NCSC has a number of mitigation techniques that they recommend. For instance, they have found that the most common DNS hijacking takes place at the registrar level, simply by gaining unauthorized access to a registrant's account. This is usually done by the standard kinds of methods like phishing, credential stuffing and social engineering.

They recommend deploying Multi-Factor Authentication (MFA) when available.

Other preventative methods can be taken, as well. An organization can regularly audit who can access the registrar control panel and make changes with the registrar. Controlling legitimate access to the registrar is a very important step.

Another important, but often overlooked step, is realizing that domain registrations typically have four points of contact: the registrant, technical, administrative, and billing contacts. An organization must ensure that all contact information is up to date. This is non-trivial, since contact updates are often overlooked when an organizations grows, shrinks, moves, or is acquired. A registrar may send certain types of communication to only one of those roles, and in some disputes, the registrant contact usually takes precedence.

Many registries offer a "registrar lock" service. This lock prevents the domain being transferred to a new owner, without the lock being removed. This is an additional level of protection whereby changes cannot be made until additional authentication has taken place which usually involves a call to the owner.

DNS can be an easy to exploit portal into your organization. Paying attention to the details of it rather than just assuming it will do things automagically is the only secure path an organization has.

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/14/2020
Lock-Pickers Face an Uncertain Future Online
Seth Rosenblatt, Contributing Writer,  8/10/2020
Hacking It as a CISO: Advice for Security Leadership
Kelly Sheridan, Staff Editor, Dark Reading,  8/10/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
7 New Cybersecurity Vulnerabilities That Could Put Your Enterprise at Risk
In this Dark Reading Tech Digest, we look at the ways security researchers and ethical hackers find critical vulnerabilities and offer insights into how you can fix them before attackers can exploit them.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-17475
PUBLISHED: 2020-08-14
Lack of authentication in the network relays used in MEGVII Koala 2.9.1-c3s allows attackers to grant physical access to anyone by sending packet data to UDP port 5000.
CVE-2020-0255
PUBLISHED: 2020-08-14
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2020-10751. Reason: This candidate is a duplicate of CVE-2020-10751. Notes: All CVE users should reference CVE-2020-10751 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidenta...
CVE-2020-14353
PUBLISHED: 2020-08-14
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2017-18270. Reason: This candidate is a duplicate of CVE-2017-18270. Notes: All CVE users should reference CVE-2017-18270 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidenta...
CVE-2020-17464
PUBLISHED: 2020-08-14
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.
CVE-2020-17473
PUBLISHED: 2020-08-14
Lack of mutual authentication in ZKTeco FaceDepot 7B 1.0.213 and ZKBiosecurity Server 1.0.0_20190723 allows an attacker to obtain a long-lasting token by impersonating the server.