DNS Cache Poisoning
How DNS Works Cached, or look … Who is ‘twitter.com’? “Authoritative” DNS Server Name IP www.twitter.com 104.244.42.1 www.rit.edu 129.21.1.40
How DNS Works (spoofed) Cached, or look … Who is ‘twitter.com’? “Authoritative” DNS Server Name IP www.twitter.com 104.244.42.1 www.rit.edu 129.21.1.40 www.chase.com ? Name IP www.twitter.com 104.244.42.1 www.rit.edu 129.21.1.40 www.chase.com 130.55.5.5 130.55.5.5 Fake DNS response to insert bogus name lookup into cache
Cache TTL DNS servers also have a “Time to Live” Basically, how long to keep the cached data By modifying TTL, the spoofed data can stay in the cache much longer, extending the time of the attack!
A famous but almost intentional attack Cached, or look … Who is ‘twitter.com’? Network traffic in China is restricted by blocking certain sites The country level DNS server is one way sites like twitter may be blocks by redirecting traffic All Chinese network traffic The IPS started pointing to the Chinese DNS server, effectively spoofing itself! “Authoritative” DNS Server [China] If twitter.com, redirect to Chinese page Non Chinese IPS Normal DNS Server