A flaw in a software tool used to translate text-based Internet domain names into numerical addresses could make parts of the Internet vulnerable to denial-of-service attacks, the Computer Emergency Response Team warned Tuesday.
The flaw is in certain versions of BIND [Berkeley Internet Name Domain], a widely-used piece of DNS software, CERT said in an advisory.
DNS servers running BIND 9 prior to Version 9.2.1 are vulnerable. An attacker could shut down the DNS service on that server by sending a specific DNS packet. The service will then remain unavailable until restarted, CERT said.
BIND 9.2.1 was released on May 1 by the Internet Software Consortium (ISC), which distributes BIND free of charge. It is a so-called maintenance release that fixes a number of bugs in 9.2.0 but has no new features, according to the ISC Web site.
DNS servers translate text-based domain names into numeric IP addresses. When those servers go down, users who type Web addresses - such as nba.com and fbi.gov - can't connect to the intended servers. E-mail sent to affected domains will bounce back.
"If you can trigger something that shuts down the name server, than that is a serious matter," said Petur Petursson, CEO of Men & Mice, a DNS consultancy firm in Reykjavik, Iceland.
"It is normal for a company to run two name servers. If you manage to shoot both of them down, the company will disappear from the Internet," Petursson said.
BIND 9.2.1 is available for free download from the ISC Web site. BIND is also often part of software sold by server software vendors. These vendors may offer their own patches, according to CERT, which urges users of BIND 9 to either upgrade or apply a patch.
The vulnerability of the DNS is seen as an important Internet security concern. The Internet Corporation for Assigned Names and Numbers, the organization that oversees the Internet's addressing system, has formed a security committee aimed, in part, at examining DNS security holes.
The IDG News Service is a Network World affiliate.
RELATED LINKS
Error 404--Not Found |
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:10.4.5 404 Not FoundThe server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. |
Apply for your free subscription to Network World. Click here. Or get Network World delivered in PDF each week.
Request a reprint or permission to use this article.
