DNS Review Quiz. Match the term to the description: A. Transfer of authority for/to a subdomain. Domain name DNS zone Delegation C B A

Similar documents
Internet Security: How the Internet works and some basic vulnerabilities

Internet Security: How the Internet works and some basic vulnerabilities. Slides from D.Boneh, Stanford and others

Computer Security CS 426

Network security. CSE 127 Computer Security. TCP/IP Protocol Stack. Packet Switched Network Architecture. Protocols are structured in layers

DNS and BGP. CS642: Computer Security. Professor Ristenpart h9p:// rist at cs dot wisc dot edu. University of Wisconsin CS 642

Domain Name System.

This time. Digging into. Networking. Protocols. Naming DNS & DHCP

DNS and BGP. CS642: Computer Security. Professor Ristenpart h9p:// rist at cs dot wisc dot edu. University of Wisconsin CS 642

CSE 565 Computer Security Fall 2018

Ordinary DNS: A? k.root-servers.net. com. NS a.gtld-servers.net a.gtld-servers.net A Client's Resolver

DNS and HTTP. A High-Level Overview of how the Internet works

An Overview of DNSSEC. Cesar Diaz! lacnic.net!

Outline NET 412 NETWORK SECURITY PROTOCOLS. Reference: Lecture 7: DNS Security 3/28/2016

CSC 574 Computer and Network Security. DNS Security

Hoda Rohani Anastasios Poulidis Supervisor: Jeroen Scheerder. System and Network Engineering July 2014

DNS Mark Kosters Carlos Martínez {ARIN, LACNIC} CTO

DNS Basics BUPT/QMUL

Introduction to Network. Topics

ECE 650 Systems Programming & Engineering. Spring 2018

2008 DNS Cache Poisoning Vulnerability Cairo, Egypt November 2008

DNSSEC DNS SECURITY EXTENSIONS INTRODUCTION TO DNSSEC FOR SECURING DNS QUERIES AND INFORMATION

Domain Name Service. DNS Overview. October 2009 Computer Networking 1

OFF-PATH ATTACKS AGAINST PUBLIC KEY INFRASTRUCTURES. Markus Brandt, Tianxiang Dai, Elias Heftrig, Amit Klein, Haya Shulman, Michael Waidner

Network Security Part 3 Domain Name System

Internet Engineering. DNS Message Format. Contents. Robert Elz.

Client Server Concepts, DNS, DHCP

A Security Evaluation of DNSSEC with NSEC Review

CS 3640: Introduction to Networks and Their Applications

DNS Security DNSSEC. * zo.net/papers/dnssec/dnss ec.html. IT352 Network Security Najwa AlGhamdi

CS 356 Using Cryptographic Tools to Secure the Domain Name System (DNS) Spring 2017

CS 3640: Introduction to Networks and Their Applications

Attacks on DNS: Risks of Caching

DNS & Iodine. Christian Grothoff.

DOMAIN NAME SECURITY EXTENSIONS

Domain Name System (DNS) Session-1: Fundamentals. Joe Abley AfNOG Workshop, AIS 2017, Nairobi

Overview. Last Lecture. This Lecture. Next Lecture. Scheduled tasks and log management. DNS and BIND Reference: DNS and BIND, 4 th Edition, O Reilly

CSCI-1680 DNS Rodrigo Fonseca

DNS Concepts. Acknowledgements July 2005, Thimphu, Bhutan. In conjunction with SANOG VI. Bill Manning Ed Lewis Joe Abley Olaf M.

CSE 127 Computer Security

More on DNS and DNSSEC

CS Paul Krzyzanowski

Computer Security. 11. Network Security. Paul Krzyzanowski. Rutgers University. Spring 2018

TCP/IP SECURITY GRAD SEC NOV

Network Security Protocols and Defensive Mechanisms

OSI Session / presentation / application Layer. Dr. Luca Allodi - Network Security - University of Trento, DISI (AA 2015/2016)

A DNS Tutorial

CS4700/5700: Network fundamentals

0 0& Basic Background. Now let s get into how things really work!

Objectives. Upon completion you will be able to:

CIS 551 / TCOM 401 Computer and Network Security

UMSSIA LECTURE II: NETWORKS?

Domain Name System (DNS) DNS Fundamentals. Computers use IP addresses. Why do we need names? hosts.txt does not scale. The old solution: HOSTS.

Local DNS Attack Lab. 1 Lab Overview. 2 Lab Environment. 2.1 Install and configure the DNS server. SEED Labs Local DNS Attack Lab 1

Chapter 19. Domain Name System (DNS)

More Internet Support Protocols

DNS Mark Kosters Carlos Martínez ARIN - LACNIC

IP ADDRESSES, NAMING, AND DNS

CSCE 463/612 Networks and Distributed Processing Spring 2018

page 1 Plain Old DNS WACREN, DNS/DNSSEC Regional Workshop Ouagadougou, October 2016

DNSSEC Trust tree: (A) ---dnslab.org. (DS keytag: 9247 dig (DNSKEY keytag. ---org. (DS keytag: d

DNS Security. * pers/dnssec/dnssec.html. IT352 Network Security Najwa AlGhamdi

Computer Networking: Applications George Blankenship. Applications George Blankenship 1

DNS: Useful tool or just a hammer? Paul DNS-OARC 06 Oct 2013, Phoenix

Protecting DNS Critical Infrastructure Solution Overview. Radware Attack Mitigation System (AMS) - Whitepaper

DNSSEC. CS 161: Computer Security Prof. David Wagner. April 11, 2016

Domain Name System (DNS) Session-1: Fundamentals. Computers use IP addresses. Why do we need names? hosts.txt does not scale

Networking Applications

Goal of this session

DNS. Introduction To. everything you never wanted to know about IP directory services

Weaver. Computer Science 161 Fall Network Security 3

Remote DNS Cache Poisoning Attack Lab

CSCI-1680 DNS Rodrigo Fonseca

ECE 435 Network Engineering Lecture 7

DNS and BGP. CS642: Computer Security. Professor Ristenpart h9p:// rist at cs dot wisc dot edu. University of Wisconsin CS 642

Root Servers. Root hints file come in many names (db.cache, named.root, named.cache, named.ca) See root-servers.org for more detail

Managing Caching DNS Server

EECS 122: Introduction to Computer Networks DNS and WWW. Internet Names & Addresses

Configuring DNS. Finding Feature Information. Prerequisites for Configuring DNS

BIG-IP DNS Services: Implementations. Version 12.0

The State and Challenges of the DNSSEC Deployment. Eric Osterweil Michael Ryan Dan Massey Lixia Zhang

ICS 351: Networking Protocols

BIND-USERS and Other Debugging Experiences. Mark Andrews Internet Systems Consortium

Security Impact of DNS Delegation Structure and Configuration Problems

DNS Cache Poisoning Looking at CERT VU#800113

DNS SECurity Extensions technical overview

CSCE 463/612 Networks and Distributed Processing Spring 2018

DNS/DNSSEC Workshop. In Collaboration with APNIC and HKIRC Hong Kong. Champika Wijayatunga Regional Security Engagement Manager Asia Pacific

BIG-IP DNS Services: Implementations. Version 12.1

network security cs642 computer security adam everspaugh

Domain Name System Security

The Internet. Overview. Network building blocks

RFC 2181 Ranking data and referrals/glue importance --- new resolver algorithm proposal ---

Network Working Group

Protecting Privacy: The Evolution of DNS Security

ROOT SERVERS MANAGEMENT AND SECURITY

CSE 127: Computer Security Network Security. Kirill Levchenko

Welcome! Acknowledgements. Introduction to DNS. cctld DNS Workshop October 2004, Bangkok, Thailand

Transport: How Applications Communicate

DNS Security. Ch 1: The Importance of DNS Security. Updated

Local DNS Attack Lab. 1 Lab Overview. 2 Lab Tasks (Part I): Setting Up a Local DNS Server. SEED Labs Local DNS Attack Lab 1

Transcription:

DNS Review Quiz Match the term to the description: C B A Level: Domain name DNS zone Delegation Descriptions: A. Transfer of authority for/to a subdomain B. A set of names under the same authority (ie.com ) C. A name in the DNS format

DNS: Hierarchical Name Space root org net edu com uk ca wisc ucb gt cmu mit cs ee www

DNS: DNS Root Name Servers

DNS: DNS Lookup Example www.cc.gatech.edu root & edu DNS Server Client Local DNS Resolver NS cc.gatech.edu gatech.edu DNS Server cc.gatech.edu DNS Server

DNS: DNS Lookup Example DNS record types (partial list): NS: name server (points to other server) A: address record (contains IP address) MX: address in charge of handling email TXT: generic text (e.g. used to distribute site public keys (DKIM)

DNS Caching Quiz Fill in the blanks: Changing a domain name into an IP address involves a large number of steps. To save time, the records are cached on a local server for reuse later. Each record has a TTL that states how long a record can be kept for future use.

Caching DNS responses are cached Quick response for repeated translations Note: NS records for domains also cached DNS negative queries are cached Save time for nonexistent sites, e.g. misspelling Cached data periodically times out Lifetime (TTL) of data controlled by owner of data TTL passed with every record

32 bits DNS Packet ver hlen TOS Pkt len Identification flg fragment offset TTL protocol header checksum Source port UDP length Source IP address Destination IP address Query ID Q R Opcode A A Question count Authority count Destination port UDP cksum T A R D R A Z xcode Answer count Addl. Record count DNS question or answer data IP Header UDP Header DNS data Query ID: 16 bit random value Links response to query

DNS Packet: Resolver to NS request 32 bits IP UDP ver hlen TOS pkt len identification flg fragment offset TTL protocol header checksum src IP 68.94.156.1 dst IP 198.26.92.30 src port = 5798 dst port = 53 UDP length UDP cksum dnsr1.sbcglobal.net c.gtld-servers.net RD=1 recursion desired QID = 43561 0 Op=0 A A T C 1 R A Z xcode OP=0 standard query Question count = 1 Answer count = 0 Authority count = 0 Addl. Record count = 0 QR=0 this is a query Qu What is A record for www.unixwiz.net?

DNS Packet: Response to Resolver 32 bits 32 bits ver hlen TOS Pkt len ver hlen TOS pkt len Identification flg fragment offset IP UDP identification flg fragment offset TTL protocol header checksum src IP 68.94.156.1 dst IP 198.26.92.30 src port = 5798 dst port = 53 UDP length QID = 43561 0 Op=0 A A UDP cksum T C 1 R A Z xcode Response contains IP addr of next NS server (called glue ) IP UDP TTL protocol header checksum src IP 192.26.92.30 dst IP 68.94.156.1 src port = 53 dst port = 5798 UDP length QID = 43561 1 Op=0 0 T A UDP cksum R D 0 Z Question count = 1 Answer count = 0 rc=ok Authority count = 2 Addl. Record count = 2 Qu What is A record for www.unixwiz.net? Question count = 1 Answer count = 0 Au unixwix.net NS = linux.unixwiz.net 2dy Authority count = 0 Addl. Record count = 0 Qu What is A record for www.unixwiz.net? Au unixwix.net NS = cs.unixwiz.net 2dy Ad linux.unixwix.net A = 64.170.162.98 1hr Ad cs.unixwix.net A = 8.7.25.94 1hr

DNS Packet: Response to Resolver 32 bits IP UDP Glue Records ver hlen TOS Pkt len Identification flg fragment offset TTL protocol header checksum src IP 192.26.92.30 dst IP 68.94.156.1 src port = 53 dst port = 5798 UDP length QID = 43561 1 Op=0 0 T A UDP cksum R D 0 Z Question count = 1 Answer count = 0 rc=ok Authority count = 2 Addl. Record count = 2 Qu What is A record for www.unixwiz.net? Au unixwix.net NS = linux.unixwiz.net 2dy Au unixwix.net NS = cs.unixwiz.net 2dy Ad linux.unixwix.net A = 64.170.162.98 1hr Ad cs.unixwix.net A = 8.7.25.94 1hr TTL c.gtld-servers.net dnsr1.sbcglobal.net QR=1 this is a response AA=0 not authoritive RA=0 recursion unavailable

DNS Packet: Authoritative Response 32 bits ver hlen TOS Pkt len Identification flg fragment offset linux.unixwiz.net FINAL ANSWER IP UDP TTL protocol header checksum src IP 64.170.162.98 dst IP 68.94.156.1 src port = 53 dst port = 5798 UDP length QID = 43561 1 Op=0 1 T A UDP cksum R D 0 Z Question count = 1 Answer count = 1 rc=ok Authority count = 2 Addl. Record count = 2 Qu What is A record for www.unixwiz.net? An www.unixwiz.net A = 8.7.25.94 1hr Au unixwix.net NS = linux.unixwiz.net 2dy Au unixwix.net NS = cs.unixwiz.net 2dy Ad linux.unixwix.net A = 64.170.162.98 1hr Ad cs.unixwix.net A = 8.7.25.94 1hr dnsr1.sbcglobal.net QR=1 this is a response AA=1 Authoritative! RA=0 recursion unavailable bailiwick checking: response is cached if it is within the same domain of query (i.e. a.com cannot set NS for b.com)

DNS Quiz Select the true statements about DNS: DNS stores the IP address. For security reasons the domain name is stored somewhere else. All domain names and IP addresses are stored at the Central Registry. It can take several days for information to propagate to all DNS servers.

Basic DNS Vulnerabilities Users/hosts trust the host-address mapping provided by DNS: Used as basis for many security policies: Browser same origin policy, URL address Obvious problems Interception of requests or compromise of DNS servers can result in incorrect or malicious responses e.g.: malicious access point in a Cafe Solution authenticated requests/responses Provided by DNSsec but few use DNSsec (yet)

Basic DNS Vulnerabilities: Cache Poisoning Basic idea: give DNS servers false records and get it cached DNS uses a 16-bit request identifier to pair queries with answers Cache may be poisoned when a name server: Disregards identifiers Has predictable ids Accepts unsolicited DNS records

Traditional Poisoning Attack Local Resolver ns1.google.com www.google.com = 74.125.157.104 TXID = 12345 A1 A2 If first attempt is not successful, attacker needs to wait for TTL before retrying!

Kaminsky s Poisoning Attack Local Resolver ns1.google.com $RAND.www.google.com = NX TXID = 12345 $RAND.www.google.com = (unknown) Ask www.google.com = 6.6.6.6 TXID = xxxx A1 A2

DNS Defenses Increase Query ID size Randomize src port, additional 11 bits Now attack takes several hours Ask every DNS query twice: Attacker has to guess QueryID correctly twice (32 bits) But DNS system cannot handle the load Deploy DNSSEC (eventually)

DNSSEC Guarantees: Authenticity of DNS answer origin Integrity of reply Authenticity of denial of existence Accomplishes this guarantee by signing DNS replies at each step of the way Uses public-key cryptography to sign responses Typically use trust anchors, entries in the operating system to bootstrap the process

DNSSEC: DNS Signing Resolve wikipedia.org. 2. IP address of.org public key of.org signature. (IP,PK) 3. Request wikipedia.org.org 1. Request wikipedia.org DNS Resolver 4. IP address of wikipedia.org, signature.org (IP) wikipedia.org

<iframe src=" http://www.evil.com "> DNS Rebinding Attack www.evil.com? DNS-SEC cannot stop this attack Firewall 171.64.7.115 TTL = 0 192.168.0.100 ns.evil.com DNS server 192.168.0.100 corporate web server www.evil.com web server Read permitted: it s the same origin 171.64.7.115

DNS Rebinding Attack: Defenses Browser mitigation: DNS Pinning Refuse to switch to a new IP Interacts poorly with proxies, VPN, dynamic DNS, Not consistently implemented in any browser

DNS Rebinding Attack: Defenses Server-side defenses Check Host header for unrecognized domains Authenticate users with something other than IP

DNS Rebinding Attack: Defenses Firewall defenses External names can t resolve to internal addresses Protects browsers inside the organization

DNS Rebinding Quiz Select all the true statements about rebinding attacks: The attacker needs to register a domain and delegate it to a server under his control. The attacker s server responds with a short TTL record. A short TTL means the page will be quickly cached. The attacker exploits the same origin policy.