Vulnerabilities / Threats
12/7/2010
12:23 PM
50%
50%

99.98% Of Domains Unsigned By DNS Security Extensions

While adoption of DNSSEC has increased, very few sites are safeguarding their servers against outages or attacks, finds new study.

Use of the Domain Name System Security Extensions (DNSSEC) specifications for securing domain names increased by 340% from 2009 to 2010. Even so, only 0.02% of Internet zones are now being signed with DNSSEC, and 23% of those are using expired signatures.

Those results come from a new study released by networking automation vendor InfoBlox and Internet testing and monitoring tool vendor the Measurement Factory.

While all Internet traffic -- browsing, checking email or conducting e-commerce transactions -- gets routed through domain name servers, the study found that organizations are doing little to safeguard those servers against attacks or outages. "This year's survey results -- along with recent related outages like those experienced by Rollingstone.com and Comcast -- should represent a huge wakeup call for any organization with an Internet presence," said Cricket Liu, VP of architecture at Infoblox, in a statement.

He was referring to Comcast subscribers recently suffering multiple, widespread outages due to a faulty domain name server. Notably, Comcast appeared to lack sufficient DNS server diversity to have prevented such failures from occurring.

On a similar note, the survey found little redundancy in authoritative domain name servers. Almost 75% of all name servers, for example, are only advertised in a single, autonomous system, which creates a single point of failure if there's a hiccup in the routing infrastructure.

While DNSSEC adoption remains low, security experts increasingly point to it as an essential step for securing domain names and preventing the types of incidents which led to 1% to 2% of global network prefixes being routed through Chinese servers in April 2010.

According to Liu, "DNSSEC implements an automated trust infrastructure, enabling systems to verify the authenticity of DNS information, and foils attackers' attempts to direct users to alternate sites for collection of credit card information and passwords, to redirect email or otherwise compromise applications."

"DNSSEC is an essential tool in sealing DNS vulnerabilities and mitigating DNS cache poisoning attacks that undermine the integrity of the DNS system," said Matt Larson, VP of DNS research at VeriSign, which sells a DNSSEC signing service, and which also manages two of the world's 13 Internet root servers. "Especially as top-level zones -- including .NET imminently and .COM early next year -- are signed, DNSSEC offers the best protection for all organizations with a presence on the Internet."

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6501
Published: 2015-03-30
The default soap.wsdl_cache_dir setting in (1) php.ini-production and (2) php.ini-development in PHP through 5.6.7 specifies the /tmp directory, which makes it easier for local users to conduct WSDL injection attacks by creating a file under /tmp with a predictable filename that is used by the get_s...

CVE-2014-9652
Published: 2015-03-30
The mconvert function in softmagic.c in file before 5.21, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not properly handle a certain string-length field during a copy of a truncated version of a Pascal string, which might allow remote atta...

CVE-2014-9653
Published: 2015-03-30
readelf.c in file before 5.22, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not consider that pread calls sometimes read only a subset of the available data, which allows remote attackers to cause a denial of service (uninitialized memory ...

CVE-2014-9705
Published: 2015-03-30
Heap-based buffer overflow in the enchant_broker_request_dict function in ext/enchant/enchant.c in PHP before 5.4.38, 5.5.x before 5.5.22, and 5.6.x before 5.6.6 allows remote attackers to execute arbitrary code via vectors that trigger creation of multiple dictionaries.

CVE-2014-9709
Published: 2015-03-30
The GetCode_ function in gd_gif_in.c in GD 2.1.1 and earlier, as used in PHP before 5.5.21 and 5.6.x before 5.6.5, allows remote attackers to cause a denial of service (buffer over-read and application crash) via a crafted GIF image that is improperly handled by the gdImageCreateFromGif function.

Dark Reading Radio
Archived Dark Reading Radio
Good hackers--aka security researchers--are worried about the possible legal and professional ramifications of President Obama's new proposed crackdown on cyber criminals.