Category: 

What is Cache Poisoning?

Article Details
  • Written By: Jacob Queen
  • Edited By: Lauren Fritsky
  • Last Modified Date: 24 September 2016
  • Copyright Protected:
    2003-2016
    Conjecture Corporation
  • Print this Article
Free Widgets for your Site/Blog
The atmosphere of Jupiter's moon Io collapses every time it is eclipsed by the planet.   more...

September 29 ,  2008 :  The Dow Jones Industrial Average experienced its largest one-day drop in history.  more...

Cache poisoning is the term used to describe a common malicious attack against domain name servers (DNS). When poisoning a DNS cache, the hacker is basically placing false data into the DNS server, which can send people to websites they weren’t intending to visit. Certain vulnerabilities have made it difficult for DNS operators to defend against this kind of assault, and hackers have many ways of using this approach for nefarious purposes.

The DNS system can be seen as a middleman between the Internet and the users. When people type in a World Wide Web address, it is usually sent to a local DNS server, which determines the Internet protocol (IP) address is for that website. Internet protocol addresses are a series of numbers, each between one and three digits, separated by dots. In many cases, local DNS servers may not have every address stored locally, so they may might contact a master server to get IP addresses for many requests.

Ad

Cache poisoning assaults are usually focused on local DNS servers rather than master servers, partly because they aren’t always as well-secured. There are many different ways for a hacker to poison a DNS cache. For example, if the individual has physical access to the DNS server, he or she could simply alter the cache directly. Another approach is for the hacker to spam the server with fake responses that are formatted as though they come from a master server. Local DNS servers can have a lot of trouble telling the difference between authentic responses and fakes, so they may simply believe that the responses in question are real and add them to the cache.

Sometimes DNS cache poisoning can be fairly random, but often hackers target specific sites. When a hacker targets a specific site, his goal might be to create a fake website that looks identical. This can be used to steal valuable user information like passwords and other things.

Another purpose for cache poisoning may be to send people to websites contaminated with malware. This can include everything from spyware to keyloggers and other software that violates an individual's privacy. Often, web users are wary and clever about avoiding malware infection, but when they visit trusted websites, they may be less vigilant. Hackers are often able to use cache poisoning to make users believe that they are visiting trusted websites when they really aren’t.

Ad

You might also Like

Recommended

Discuss this Article

Post your comments

exception 'Exception' with message 'error writing captcha: Duplicate entry '2147483647' for key 'PRIMARY'' in /ssd/www/wisegeek/public_html/_core/classes/public/Captcha.php:44
Stack trace:
#0 /ssd/www/wisegeek/public_html/_core/controls/public/ControlDiscussionPostBox.php(324): Captcha->createCaptcha()
#1 /ssd/www/wisegeek/public_html/framework/classes/Control.php(104): ControlDiscussionPostBox->preRender(false)
#2 /ssd/www/wisegeek/public_html/framework/classes/Control.php(149): Control->render()
#3 /ssd/www/wisegeek/public_html/tpl/default-nocustom-lu/pages/public/article/article.htm(526): Control->__toString()
#4 /ssd/www/wisegeek/public_html/framework/classes/Control.php(300): require('/ssd/www/wisege...')
#5 /ssd/www/wisegeek/public_html/framework/classes/Control.php(309): Control->requireTpl('pages/public/ar...', Object(PageArticleCom), true)
#6 /ssd/www/wisegeek/public_html/framework/classes/Control.php(131): Control->renderTpl('pages/public/ar...', Object(PageArticleCom))
#7 /ssd/www/wisegeek/public_html/framework/classes/FormDataControl.php(87): Control->renderTemplate()
#8 /ssd/www/wisegeek/public_html/framework/classes/Control.php(109): FormDataControl->renderTemplate()
#9 /ssd/www/wisegeek/public_html/framework/classes/ScriptPage.php(50): Control->render(false)
#10 /ssd/www/wisegeek/public_html/framework/classes/Control.php(149): ScriptPage->render()
#11 /ssd/www/wisegeek/public_html/framework/classes/Page.php(97): Control->__toString()
#12 /ssd/www/wisegeek/public_html/_core/classes/public/PublicFrontController.php(443): Page->processRequest()
#13 /ssd/www/wisegeek/public_html/_core/classes/public/PublicFrontController.php(7): PublicFrontController->renderPage()
#14 /ssd/www/wisegeek/public_html/index.php(11): PublicFrontController::run()
#15 {main}