Attacks/Breaches
8/30/2013
06:52 PM
Ehsan Foroughi
Ehsan Foroughi
Commentary
50%
50%

Thwart DNS Hijackers: 5 Tips

Domain name system attacks hit The New York Times and Twitter hard last month. Here are five ways to make your DNS records harder to hack and easier to recover if they're compromised.

The Syrian Electronic Army: 9 Things We Know
(click image for larger view)
The Syrian Electronic Army: 9 Things We Know
In light of the recent domain name system (DNS) hijacking attacks on The New York Times, Twitter and Huffington Post, it's important for CIOs to take a closer look at their DNS security strategy -- and to be able to respond quickly if their company is attacked.

DNS records are basically sets of instructions that help connect your website to the outside world. The following five practices make these records harder to hijack and easier to recover if they are compromised, thereby reducing the damage attackers can cause. When DNS records are hijacked, a company must be able to get them back as quickly as possible because once the malicious records hit the caching servers, it becomes much harder to undo the damage.

1. Use best practices for credentials that allow changes to be made to DNS records.

Your whole service is only as secure as the security of the password to your DNS registrant account. Ensure that access to accounts used to update DNS records is limited to as few people in your organization as possible. Make sure to use hard-to-guess passwords, and avoid reusing passwords at all costs.

[ Here's why you shouldn't buy Android apps from off-brand sites. Read Hack 99% Of Android Devices: Big Vulnerability. ]

2. Revisit the choice of DNS provider regularly as you grow.

Many companies, particularly start-ups, frequently choose DNS registrants and DNS service providers based on a combination of their pricing and the ease of setup and use. Sometimes that means the DNS provider doesn't have much information about the owner other than a username and password used to identify the account. In cases of social engineering attacks or compromised passwords, it might be hard to reclaim the domain.

As companies grow, they should revisit their choice of provider every few months to make sure that it's capable of handling the level of security the company needs. Popular and high-profile services might be targeted by hackers with agendas -- and not every provider is capable of handling the heat that comes with popularity.

3. Make use of SSL certificates.

DNS hijacking can effectively be used to perform man-in-the-middle (MITM) attacks. In a MITM attack, the attacker diverts the user to a malicious server he controls. The malicious server then sends the user's request to the original server and sends the server's response back to the user. This setup allows the attacker to steal the information being passed back and forth, inject malicious content into responses before sending them back to the user, or both.

This is one of the highest risks associated with DNS hijacking and can cause a lot of damage in the form of stolen credentials and injection of malicious content.

To arm yourself, enforce validation of SSL/TLS certificates and use certificate pinning in mobile apps and rich clients. Certificate validation means the attacker must get a certificate tied to the stolen domain before being able to carry out the MITM attack. Pinning certificates in mobile and rich clients will take this restriction even further by ensuring the attacker will need access to the pinned certificate's private keys before being able to carry out the attack. This will reduce the risk of a MITM attack, which means the DNS hijack will do much less prolonged damage.

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-0547
Published: 2015-07-04
The D2CenterstageService.getComments service method in EMC Documentum D2 4.1 and 4.2 before 4.2 P16 and 4.5 before P03 allows remote authenticated users to conduct Documentum Query Language (DQL) injection attacks and bypass intended read-access restrictions via unspecified vectors.

CVE-2015-0548
Published: 2015-07-04
The D2DownloadService.getDownloadUrls service method in EMC Documentum D2 4.1 and 4.2 before 4.2 P16 and 4.5 before P03 allows remote authenticated users to conduct Documentum Query Language (DQL) injection attacks and bypass intended read-access restrictions via unspecified vectors.

CVE-2015-0551
Published: 2015-07-04
Multiple cross-site scripting (XSS) vulnerabilities in EMC Documentum WebTop 6.7SP1 before P31, 6.7SP2 before P23, and 6.8 before P01; Documentum Administrator 6.7SP1 before P31, 6.7SP2 before P23, 7.0 before P18, 7.1 before P15, and 7.2 before P01; Documentum Digital Assets Manager 6.5SP6 before P2...

CVE-2015-1966
Published: 2015-07-04
Multiple cross-site scripting (XSS) vulnerabilities in IBM Tivoli Federated Identity Manager (TFIM) 6.2.0 before FP17, 6.2.1 before FP9, and 6.2.2 before FP15, as used in Security Access Manager for Mobile and other products, allow remote attackers to inject arbitrary web script or HTML via a crafte...

CVE-2015-4196
Published: 2015-07-04
Platform Software before 4.4.5 in Cisco Unified Communications Domain Manager (CDM) 8.x has a hardcoded password for a privileged account, which allows remote attackers to obtain root access by leveraging knowledge of this password and entering it in an SSH session, aka Bug ID CSCuq45546.

Dark Reading Radio
Archived Dark Reading Radio
Marc Spitler, co-author of the Verizon DBIR will share some of the lesser-known but most intriguing tidbits from the massive report