1 Email and DNS Hacking. Overview Email Hacking - Technology - Attacks - Phishing/Spearphishing/Whaling DNS Hacking - Technology - Attacks - Flux 2.

Slides:



Advertisements
Similar presentations
Review iClickers. Ch 1: The Importance of DNS Security.
Advertisements

© NLnet Labs, Licensed under a Creative Commons Attribution 3.0 Unported License.Creative Commons Attribution 3.0 Unported License Introduction.
Sergei Komarov. DNS  Mechanism for IP hostname resolution  Globally distributed database  Hierarchical structure  Comprised of three components.
Securing Bruce Maggs. Separate Suites of Protocols Protocols for retrieving POP, IMAP, MAPI (Microsoft Exchange) Protocols for sending
More on SSL/TLS. Internet security: TLS TLS is one of the more prominent internet security protocols. TLS is one of the more prominent internet security.
2.1 Installing the DNS Server Role Overview of the Domain Name System Role Overview of the DNS Namespace DNS Improvements for Windows Server 2008 Considerations.
Domain Name System. DNS is a client/server protocol which provides Name to IP Address Resolution.
Computer Networks: Domain Name System. The domain name system (DNS) is an application-layer protocol for mapping domain names to IP addresses Vacation.
70-294: MCSE Guide to Microsoft Windows Server 2003 Active Directory, Enhanced Chapter 2: Name Resolution and DNS.
Domain Name System (DNS) Network Information Center (NIC) : HOSTS.TXT.
Phishing – Read Behind The Lines Veljko Pejović
Domain Name System: DNS
Domain Name System ( DNS )  DNS is the system that provides name to address mapping for the internet.
Dave Roberts.  Dynamic Host Configuration Protocol  DHCP  Simple Mail Transport Protocol  SMTP 2.
Confidentiality (slides courtesy of Danny Lungstrom and Senthil Somasundaram)
Electronic Mail Three major components: SMTP user agents mail servers
Domain Name System | DNSSEC. 2  Internet Protocol address uniquely identifies laptops or phones or other devices  The Domain Name System matches IP.
Lecturer : Ms.Trần Thị Ngọc Hoa Chapter 8 File Transfer Protocol – Simple Mail Transfer Protocol.
1 Naming with the Domain Name System. 2 Internet Applications Domain Name System Electronic mail IP telephony Remote login File transfer All use client-server.
TELE 301 Lecture 11: DNS 1 Overview Last Lecture –Scheduled tasks and log management This Lecture –DNS Next Lecture –Address assignment (DHCP)
Got DNS? A review of Domain Name Services and how it impacts website developers. By Jason Baker Digital North.
Chapter 9 - Applications We will look at three main applications DNS (name services) SMTP ( ) HTTP (World Wide Web) Our main focus will be on DNS.
Computer Networks: Domain Name System. The domain name system (DNS) is an application-layer protocol for mapping domain names to IP addresses Vacation.
IIT Indore © Neminath Hubballi
Mail Services.
Lecturer: Maxim Podlesny Sep CSE 473 File Transfer and Electronic in Internet.
SMTP PROTOCOL CONFIGURATION AND MANAGEMENT Chapter 8.
FTP (File Transfer Protocol) & Telnet
Internet applications Bill Chu. © Bei-Tseng Chu Aug 2000 Need for Domain Name Service (DNS) Natively, a TCP host is identified by its IP address hosts.
DNS: Domain Name System
October 15, 2002Serguei A. Mokhov, 1 Intro to DNS SOEN321 - Information Systems Security.
Chapter 17 Domain Name System
DNS & SPAM SHAREPOINT 2010 IT:NETWORK:APPLICATIONS.
Chapter 29 Domain Name System (DNS) Allows users to reference computer names via symbolic names translates symbolic host names into associated IP addresses.
Traditional Internet Applications Dr. John P. Abraham Professor UTRGV.
October 8, 2015 University of Tulsa - Center for Information Security Microsoft Windows 2000 DNS October 8, 2015.
We want this Internet, this global cyberspace, to be completely free, completely open. Everyone does. I do. But we also want to conduct business there,
Lecture – DNS How to find things…. Domain Name System Associate human-friendly names with machine- friendly IP addresses Resolution of a given hostname.
Naming March 8, Networks What is naming?  Associations between some elements in a set of names and some elements in a set of values  Binding.
1 Kyung Hee University Chapter 18 Domain Name System.
Application Services COM211 Communications and Networks CDA College Theodoros Christophides
Data Communications and Networks Chapter 5 – Network Services DNS, DHCP, FTP and SMTP ICT-BVF8.1- Data Communications and Network Trainer: Dr. Abbes Sebihi.
Securing Bruce Maggs. Separate Suites of Protocols Protocols for retrieving POP, IMAP, MAPI (Microsoft Exchange) Protocols for sending
Configuring Name Resolution and Additional Services Lesson 12.
1 Internet Network Services. 2 Module - Internet Network Services ♦ Overview This module focuses on configuring and customizing the servers on the network.
Unzip the attachment and double click to run it..
* Agenda  What is the DNS ?  Poisoning the cache  Short term solution  Long term solution.
DNS Cache Poisoning. History 1993 – DNS protocol allowed attacker to inject false data which was then cached 1997 – BIND 16-bit transaction ids not randomized,
DNS DNS overview DNS operation DNS zones. DNS Overview Name to IP address lookup service based on Domain Names Some DNS servers hold name and address.
SMTP Tapu Ahmed Jeremy Nunn. Basics Responsible for electronic mail delivery. Responsible for electronic mail delivery. Simple ASCII protocol that runs.
DNS Security 1. Fundamental Problems of Network Security Internet was designed without security in mind –Initial design focused more on how to make it.
4343 X2 – Outline The Domain Name System The Web.
CITA 310 Section 6 Providing Services (Textbook Chapter 8)
Ch 6: DNSSEC and Beyond Updated DNSSEC Objectives of DNSSEC Data origin authentication – Assurance that the requested data came from the genuine.
COMP2322 Lab 3 DNS Steven Lee Feb. 19, Content Understand the Domain Name System (DNS). Analyze the DNS protocol with Wireshark. 2.
COMP 431 Internet Services & Protocols
Internet Naming Service: DNS* Chapter 5. The Name Space The name space is the structure of the DNS database –An inverted tree with the root node at the.
Domain Name System INTRODUCTION to Eng. Yasser Al-eimad
Basics of the Domain Name System (DNS) By : AMMY- DRISS Mohamed Amine KADDARI Zakaria MAHMOUDI Soufiane Oujda Med I University National College of Applied.
Ch 2. Application Layer Myungchul Kim
DNS Security Risks Section 0x02. Joke/Cool thing traceroute traceroute c
Understand Names Resolution
DNS Security Issues SeongHo Cho DPNM Lab., POSTECH
IMPLEMENTING NAME RESOLUTION USING DNS
Unit 5: Providing Network Services
DNS Cache Poisoning Attack
Overview What is Spoofing Types of Spoofing
NET 536 Network Security Lecture 8: DNS Security
NET 536 Network Security Lecture 6: DNS Security
Domain Name System Refs: Chapter 9 RFC 1034 RFC 1035.
Presentation transcript:

1 and DNS Hacking

Overview Hacking - Technology - Attacks - Phishing/Spearphishing/Whaling DNS Hacking - Technology - Attacks - Flux 2

3 A postcard written in pencil, with trusted cargo attached Here is the program you’ve been waiting for. Trusted Colleague

How Works 4 User Mail User Agent Mail Transfer Agent Mail User Agent

Simple Mail Transfer Protocol TCP/25 by default Transfer-agent based Text Protocol Single connection, multiple messages (maybe) Easily forged 5 S: 220 smtp.example.com ESMTP Postfix C: HELO relay.example.org S: 250 Hello relay.example.org, I am glad to meet you C: MAIL FROM: S: 250 Ok C: RCPT TO: S: 250 Ok C: RCPT TO: S: 250 Ok C: DATA S: 354 End data with. C: From: "Bob Example" C: To: Alice Example C: Date: Tue, 15 Jan :02: C: Subject: Test message C: Hello Alice. C: Your friend, Bob C:. S: 250 Ok: queued as C: QUIT S: 221 Bye {The server closes the connection}

How Can Go Wrong 6 User Mail User Agent Mail Transfer Agent Mail User Agent Malicious Software Weak Protocol Intercepted Message Malicious Software Weak Protocol Inserted Message Preview & Download Integration with OS Dropped Message

Attacking 7 User Mail User Agent Mail Transfer Agent Mail User Agent Subvert Attach Hijack Flood Extract Insert Compromise Propagate Fool

Social Engineering Exploit trust relationships between people Exploit service climate Exploit business methods 8

9 Love Letter Virus Check out this joke... Trusted Colleague IRC Exchange VBS JPG MP3 others Replace Corrupt data/script files Steal Passwords Clog

10 Phishing example? Date: Tue, 20 Sep :06: (PDT) From: Countrywide To: Subject: Important Customer Correspondence [Image: "height="] [Image: "Countrywide - Full Speectrum Lending Division"] [Image: " "] [Image: "height="] [Image: "height="] [Image: "height="] [Image: "If you could use some extra cash, Countrywide could make it easy."] [Image: "Click Here to Get Started"] [Image: "height="] [Image: "height="] [Image: "height="] [Image: "height="] Dear Timothy, We can help customers get cash from the available equity they've built up in their homes by refinancing their mortgages ? and with the trend in rising home values, we estimate your home's equity may have increased to as much as $43, (much more…) Phone number appears legit, current mortgage holder Note typographical errors (Speectrum, empty images, etc.) Big payoff offered Closer look: embedded domains doesn’t match from domain (m0.net, r.delivery.net, not countrywide.com, all same ISP (Digital Impact))

Domain Name System More than just hostname → IP Query hierarchy of nameservers –Local nameserver (resolver): answer from cache or preloaded resolutions, may do recursive queries –Authoritative nameserver: answer based on domains it covers, or recurse –Root nameserver: answer top-level, delegate, or generate errors 11

Name Server Protocol UDP/53 or TCP/53 Client queries local (address, ptr, mx, ns, hinfo, any) Local responds from cache or queries to root Root responds with referral to TLD or error Local queries TLD TLD responds with referral to authority or error Local queries authority Authority sends answer Local sends answer 12 Query Response

Where DNS Can Go Wrong Client Side –Cache Poisoning –False Response –False Domains –Compromise –Tunneling Server Side –Flooding –False Response –Compromise 13

Flux Why would a domain change its resolution? Why would a domain change frequently? Why would a domain change transiently? 14

Summary Common and needed protocols Many, many vulnerabilities Many, many attacks Some systematic solutions (encryption) Trust 15