The road to IPv6 is generally smooth but contains a few potholes

Posted by    on   Apr 23, 2018

"The report of my death was an exaggeration," Mark Twain famously said in 1897. It was indeed: Twain went on to live for another 13 years but did eventually die.

The same is true for IPv4: reports of the pending 'ipv4pocalypse' have been doing the rounds for at least a decade (the most recent one is from a few days ago) and they have generally exaggerated the problem. Yet the fact that IPv4 addresses will eventually run out cannot be avoided.

The good news is that many devices support its successor protocol, IPv6, and that most devices and services can seamlessly switch between IPv4 and IPv6. The bad news is that this isn't true for everything.

A few years ago, I attended a conference where I connected my phone to the local Wi-Fi network. I activated my OpenVPN app, only to find a lot of traffic was bypassing the VPN. It turned out that the local network was supporting IPv6, as were many websites I was connecting to; OpenVPN at that time didn't support IPv6.

In other cases, IPv6 is supported, but works slightly differently. A blog post by Trustwave's John Anderson provides a good example of how this can be leveraged in a penetration test: access control rules for a Redis instance, which does support IPv6, were only configured using IPv4, thus allowing an attacker to connect without authentication.

Six years ago, I briefly looked at the security implications of the switch to IPv6. That article really only touched the surface and though I don't expect there to be an 'IPv6pocalypse', there will be many interesting and unforeseen edge cases, some of which may attract the attention of attackers. Don't panic about IPv6 and don't see this as a reason not to enable IPv6 – if only because you will eventually have to anyway. But do keep an eye out for the many subtleties that come with the change.

mark-twain-statue.jpgStatue of Mark Twain, Glascock's Landing, Hannibal, MO.

Copyright: brians101 / 123RF Stock Photo

twitter.png
fb.png
linkedin.png
hackernews.png
reddit.png

 

Latest posts:

VB2018 paper: From Hacking Team to hacked team to…?

Today we publish the VB2018 paper and video by ESET researcher Filip Kafka, who looked at the new malware by Hacking Team, after the company had recovered from the 2015 breach.

The spam that is hardest to block is often the most damaging

We see a lot of spam in the VBSpam test lab, and we also see how well such emails are being blocked by email security products. Worryingly, it is often the emails with a malicious attachment or a phishing link that are most likely to be missed.

Throwback Thursday: We're all doomed

Mydoom turns 15 this month, and is still being seen in email attachments. This Throwback Thursday we look back to March 2004, when Gabor Szappanos tracked the rise of W32/Mydoom.

VB2019 call for papers - now open!

Have you analysed a new online threat? Do you know a new way to defend against such threats? Are you tasked with securing systems and fending off attacks? The call for papers for VB2019 is now open and we want to hear from you!

VB2018 paper: Unpacking the packed unpacker: reversing an Android anti-analysis library

Today, we publish a VB2018 paper by Google researcher Maddie Stone in which she looks at one of the most interesting anti-analysis native libraries in the Android ecosystem. We also release the recording of Maddie's presentation.

We have placed cookies on your device in order to improve the functionality of this site, as outlined in our cookies policy. However, you may delete and block all cookies from this site and your use of the site will be unaffected. By continuing to browse this site, you are agreeing to Virus Bulletin's use of data as outlined in our privacy policy.