DNS security

DNS n’a pas été conçu dans un objectif de sécurité et de nombreux types d’attaques ont été créés pour exploiter les vulnérabilités du système DNS.

Objectifs d’apprentissage

Cet article s'articule autour des points suivants :

  • Comprendre ce qu’est le DNSSEC et son fonctionnement
  • Se familiariser avec les attaques DNS les plus courantes
  • Différentier le DNSSEC et les autres solutions de sécurité DNS

Copier le lien de l'article

Pourquoi la sécurité DNS est-elle importante ?

Les requêtes DNS standards, qui sont nécessaires pour presque tout le trafic web, créent des opportunités pour les exploits DNS, comme le détournement du DNS et les attaques en chemin (on-path). Ces attaques peuvent rediriger le trafic entrant d’un site web vers une copie falsifiée du site, collectant ainsi des informations utilisateur sensibles et exposant les entreprises à une responsabilité majeure. L'une des façons les plus connues de se protéger contre les menaces DNS est l’adoption du protocole DNSSEC.

What is DNSSEC?

Like many Internet protocols, the DNS system was not designed with security in mind and contains several design limitations. These limitations, combined with advances in technology, have made it easy for attackers to hijack a DNS lookup for malicious purposes, such as sending a user to a fraudulent website that can distribute malware or collect personal information.

DNS Security Extensions (DNSSEC) is a security protocol created to mitigate this problem. DNSSEC protects against attacks by digitally signing data to help ensure its validity. In order to ensure a secure lookup, the signing must happen at every level in the DNS lookup process.

Ce processus de signature est similaire à quelqu'un qui signe un document juridique avec un stylo. Cette personne signe de sa main en utilisant une signature unique que personne d'autre ne peut reproduire. Un expert judiciaire peut parfaitement examiner cette signature et en vérifier l'authenticité. Ces signatures numériques garantissent que les données n'ont pas été falsifiées.

Le DNSSEC met en œuvre une politique de signature numérique hiérarchique sur toutes les couches DNS. Par exemple, dans le cas d'un site « google.com » un serveur DNS racine signerait une clé pour le serveur de noms .COM, et le serveur de noms .COM signerait ensuite une clé pour le site google.com serveur de noms faisant autorité.

While improved security is always preferred, DNSSEC is designed to be backwards-compatible to ensure that traditional DNS lookups still resolve correctly, albeit without the added security. DNSSEC is meant to work with other security measures like SSL/TLS as part of a holistic Internet security strategy.

DNSSEC creates a parent-child train of trust that travels all the way up to the root zone. This chain of trust cannot be compromised at any layer of DNS, or else the request will become open to an on-path attack.

To close the chain of trust, the root zone itself needs to be validated (proven to be free of tampering or fraud), and this is actually done using human intervention. Interestingly, in what’s called a Root Zone Signing Ceremony, selected individuals from around the world meet to sign the root DNSKEY RRset in a public and audited way.

Voici une explication plus détaillée du fonctionnement du DNSSEC > > >

Quelles sont les attaques courantes impliquant le DNS ?

DNSSEC is a powerful security protocol, but unfortunately it is not currently universally adopted. This lack of adoption coupled with other potential vulnerabilities, on top of the fact that DNS is an integral part of most Internet requests, makes DNS a prime target for malicious attacks. Attackers have found a number of ways to target and exploit DNS servers. Here are some of the most common:

Usurpation du DNS/empoisonnement du cache : Il s'agit d'une attaque dans laquelle des données DNS falsifiées sont introduites dans le cache d'un résolveur DNS, ce qui a pour conséquence que le résolveur renvoie une adresse IP incorrecte pour un domaine. Plutôt que d’accéder au site web voulu, le trafic peut être dévié vers une machine malveillante ou vers tout autre site souhaité par le pirate ; il s’agit souvent d’une réplique du site d’origine utilisé à des fins malveillantes comme la distribution de logiciels malveillants ou la collecte d’informations de connexion.

DNS tunneling: This attack uses other protocols to tunnel through DNS queries and responses. Attackers can use SSH, TCP, or HTTP to pass malware or stolen information into DNS queries, undetected by most firewalls.

DNS hijacking: In DNS hijacking the attacker redirects queries to a different domain name server. This can be done either with malware or with the unauthorized modification of a DNS server. Although the result is similar to that of DNS spoofing, this is a fundamentally different attack because it targets the DNS record of the website on the nameserver, rather than a resolver’s cache.

Détournement du DNS

NXDOMAIN attack: This is a type of DNS flood attack where an attacker inundates a DNS server with requests, asking for records that do not exist, in an attempt to cause a denial-of-service for legitimate traffic. This can be accomplished using sophisticated attack tools that can auto-generate unique subdomains for each request. NXDOMAIN attacks can also target a recursive resolver with the goal of filling the resolver’s cache with junk requests.

Phantom domain attack: A phantom domain attack has a similar result to an NXDOMAIN attack on a DNS resolver. The attacker sets up a bunch of ‘phantom’ domain servers that either respond to requests very slowly or not at all. The resolver is then hit with a flood of requests to these domains and the resolver gets tied up waiting for responses, leading to slow performance and denial-of-service.

Random subdomain attack: In this case, the attacker sends DNS queries for several random, nonexistent subdomains of one legitimate site. The goal is to create a denial-of-service for the domain’s authoritative nameserver, making it impossible to lookup the website from the nameserver. As a side effect, the ISP serving the attacker may also be impacted, as their recursive resolver's cache will be loaded with bad requests.

Domain lock-up attack: Attackers orchestrate this form of attack by setting up special domains and resolvers to create TCP connections with other legitimate resolvers. When the targeted resolvers send requests, these domains send back slow streams of random packets, tying up the resolver’s resources.

Botnet-based CPE attack: These attacks are carried out using CPE devices (Customer Premise Equipment; this is hardware given out by service providers for use by their customers, such as modems, routers, cable boxes, etc.). The attackers compromise the CPEs and the devices become part of a botnet, used to perform random subdomain attacks against one site or domain.

What is the best way to protect against DNS-based attacks?

In addition to DNSSEC, an operator of a DNS zone can take further measures to secure their servers. Over-provisioning infrastructure is one simple strategy to overcome DDoS attacks. Simply put, if your nameserver can handle several multiples more traffic than you expect, it is harder for a volume-based attack to overwhelm your server.

Anycast routing is another handy tool that can disrupt DDoS attacks. Anycast allows multiple servers to share a single IP address, so even if one DNS server gets shut down, there will still be others up and serving. Another popular strategy for securing DNS servers is a DNS firewall.

Qu'est-ce qu'un pare-feu DNS ?

Un pare-feu DNS est un outil qui peut fournir plusieurs services de sécurité et de performance aux serveurs DNS. Un pare-feu DNS est érigé entre le résolveur récursif de l’utilisateur et le serveur de noms faisant autorité du site web ou du service qu'il essaie d'atteindre. Le pare-feu peut fournir des services de rate limiting pour bloquer les pirates qui tentent de submerger le serveur. Si le serveur subit un temps d'arrêt suite à une attaque ou pour toute autre raison, le pare-feu DNS peut maintenir le site ou le service de l’opérateur en utilisant les réponses DNS présentes dans le cache.

En plus de ses fonctionnalités de sécurité, un pare-feu DNS peut également fournir à l’opérateur des solutions de performance, telles que des recherches DNS plus rapides et des coûts de bande passante réduits pour l'opérateur DNS. En savoir plus sur le pare-feu DNS de Cloudflare.

DNS comme outil de sécurité

DNS resolvers can also be configured to provide security solutions for their end users (people browsing the Internet). Some DNS resolvers provide features such as content filtering, which can block sites known to distribute malware and spam, and botnet protection, which blocks communication with known botnets. Many of these secured DNS resolvers are free to use and a user can switch to one of these recursive DNS services by changing a single setting in their local router. Cloudflare DNS has an emphasis on security.

Are DNS queries private?

Another important DNS security issue is user privacy. DNS queries are not encrypted. Even if users use a DNS resolver like 1.1.1.1 that does not track their activities, DNS queries travel over the Internet in plaintext. This means anyone who intercepts the query can see which websites the user is visiting.

This lack of privacy has an impact on security and, in some cases, human rights; if DNS queries are not private, then it becomes easier for governments to censor the Internet and for attackers to stalk users' online behavior.

DNS over TLS and DNS over HTTPS are two standards for encrypting DNS queries in order to prevent external parties from being able to read them. Cloudflare DNS supports both of these standards. Cloudflare also partners with other organizations to help improve DNS security — for example, helping Mozilla enable DNS over HTTPS in its Firefox browser in order to protect users.