Perimeter
6/8/2011
01:30 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

IPv6 Graduation Day

Big Bird, Google, and Facebook participate in first high-profile test flight of new IP protocol amid DDoS threat backdrop

My first IPv6 story warning of the eventual saturation of the IPv4 address space was published a long time ago. My daughter -- who graduates from high school this weekend -- was a toddler back then. So here we are today, on World IPv6 Day, finally running a global real-world test of the next-generation IP protocol, just a couple of months before I send my firstborn off to college.

The good news about IPv6 is that unlike its predecessor -- or much of the Internet for that matter -- it was built with security in mind. IPv6 includes IPSec encryption and address space with a lot of headroom that could help prevent things like worm propagation. But the irony is that the more secure IPv6 also introduces some security issues of its own, with an architecture that's inviting to distributed denial-of-service (DDoS) attacks due to its larger headers, which require more processing by network devices, as well as the likelihood of all-new vulnerabilities in the protocol and misconfigured implementations that expose security holes.

As I write this post, there are rumblings of concern that hackers might also do a little test-drive themselves today of IPv6 to see just how easily it can be DDoS'ed. Google, Facebook, Yahoo, Cisco, and more than 400 other organizations (even Sesame Street!) are using IPv6 on their sites today in the 24-hour test flight of the 128-bit protocol, which could provide some 670 quadrillion IP addresses, experts say.

But the good news is that more people are talking about security issues surrounding the transition to IPv6. Translated: I received a lot of PR pitches over the past couple of weeks about IPv6 security implications.

Dark Reading contributing editor and blogger John Sawyer has pointed out the challenges it will bring for vulnerability scanning and penetration testing. He talks here about how new host-discovery methods will be put in place to better target vulnerability scans, for example, as well as other methods of finding IPs.

Perhaps one of the biggest problems will be its "newness." IPv6 might be nearly two decades in the making, but once users start really running it in their networks, it's sure to expose previously unknown security flaws in IPv6-based products.

The likely missteps in implementation include not allocating sufficient memory for the longer IPv6 addresses, says Rob Rachwald, which could lead to remote code execution, for example. Human error is also highly likely when handling IPv6's new configuration rules and management, he says, leaving areas of the network exposed to attackers. All it would take is one request to a server that exploits a buffer overflow flaw in an IPv6-based system, according to Rachwald, who blogged on this today. Attackers could exploit mistakes in the Internet address translation process and pose as someone within the company, or sneak past a firewall that isn't properly configured for IPv6.

But we won't know until about 8 p.m. ET tonight, when World IPv6 Day's test concludes, how IPv6 security fared in its test-entry into the real world.

-- Kelly Jackson Higgins, Senior Editor, Dark Reading Follow Kelly (@kjhiggins) here on Twitter.

Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Title Partner’s Role in Perimeter Security
Title Partner’s Role in Perimeter Security
Considering how prevalent third-party attacks are, we need to ask hard questions about how partners and suppliers are safeguarding systems and data.
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.