IPv6 keeps getting hacked on Windows

Uncover the latest cybersecurity threat with NetworkChuck as we delve into a critical IPv6 flaw affecting all Windows users. Learn how hackers can exploit this vulnerability to gain remote access without any user interaction, and discover practical steps to protect your system. From understanding the intricacies of IPV6 to exploring effective mitigation strategies, this video is a must-watch for anyone looking to safeguard their digital environment. Stay informed and secure with expert insights and actionable advice.

**Sponsored by Dashlane

SUPPORT NETWORKCHUCK
---------------------------------------------------

READY TO LEARN??
---------------------------------------------------

FOLLOW ME EVERYWHERE
---------------------------------------------------

AFFILIATES & REFERRALS
---------------------------------------------------
(GEAR I USE...STUFF I RECOMMEND)

- Critical IPV6 vulnerability explained
- Protecting Windows from IPV6 attacks
- Understanding IPV6 security risks
- How hackers exploit IPV6 flaws
- IPV6 vs IPV4: Security implications
- Mitigating IPV6 vulnerabilities
- NetworkChuck's cybersecurity tips
- Remote access threats via IPV6
- Buffer overflow and integer underflow
- Disabling IPV6 for enhanced security
- Microsoft Patch Tuesday updates
- Safeguarding against remote code execution
- IPV6 address security concerns
- The future of internet protocols
- Dual stack network vulnerabilities
- Enhancing digital security measures
- Cybersecurity best practices 2024
- The role of NAT in network security
- Understanding TCP/IP stack vulnerabilities
- How to check your IPV6 address
- Preventing wormable cyber threats
- The evolution of internet security protocols
- Practical cybersecurity advice for users
- Staying ahead of cybersecurity threats

#ipv6 #windows

[NetworkChuck]

Uncover the latest cybersecurity threat with NetworkChuck as we delve into a critical IPv6 flaw affecting all Windows users. Learn how hackers can exploit this vulnerability to gain remote access without any user interaction, and discover practical steps to protect your system. From understanding the intricacies of IPV6 to exploring effective mitigation strategies, this video is a must-watch for anyone looking to safeguard their digital environment. Stay informed and secure with expert insights and actionable advice.






**Sponsored by Dashlane

[DIYDaveOK]

In the interest of full disclosure, I think it's important to stress that this is a Windows-specific bug in their IPv6 stack, not a *general* protocol bug.

[demanuDJ]

Why we blame IPv6? Its Microsoft flaws, not IPv6... Just because Microsoft cannot handle their IPv6 stack its not the reason to blame a protocol which works flawless on Linux and Apple devices

[technopc]

Don’t blame IPv6 for Microsoft’s failures.

[Felixls]

Denying the current internet protocol is silly, they hacked a WINDOWS lame code, not IPv6.

[KevinPfeifer]

Its sad to see, that popular content creators like you are fueling the "IPv6 is bad" movement and therefore extend the "dual stack" period even more
Any technical person can understand, that the IPv6 vulnerability is Windows specific but everyone else learns that "IPv6 is bad"
there should be no good reason to not have broader IPv6 support now in 2024 other than skill issues inside ISP's, which is nothing new

[MichaelLandgraf]

"IPv6 keeps getting hacked" or rather "Windows keeps getting hacked"

[apalrdsadventures]

"Windows keeps getting hacked"!

This has nothing to do with the design of IPv6 and everything to do with bad code from Microsoft.

[WillyJL]

This makes ipv6 as a whole sound like a problem. No it's not. Windows and Microsoft are the problem. The vulnerability is in how they implemented ipv6. Also lacking some core details, yeah "integer underflow" but you can't just tell it "please do an underflow", explaining what causes the underflow would've been nice. And it's ironic how you explain that ipv6 adoption is slow, and proceed to show how to disable ipv6 thus slowing it even more. If the fix was disabling stuff nothing would ever evolve, update your stuff don't disable it.

[ShimoriUta]

0:23 Bro, it's not IPv6 fault, it's Windows and Microsoft for creating shitty spyware, I mean, software 💀

[esra_erimez]

The problem isn't with IPv6, the problem with with Microsoft's IPv6 implementation. This problem doesn't exist with Linux

[Galileocrafter]

This video feels like he never heard of a firewall, touting NAT as a security feature is bad advice. Shame of you, you should know better.

[JivanPal]

"Your device has an IPv6 address. This should scare you."

No, it shouldn't. Residential gateways have a "default deny" firewall for inbound connections. If you come across an ISP for which this isn't the case, name and shame them, please, I'm begging you, because I'm certain you won't find one.

[Deffcolony]

I’m sorry but the video thumbnail is completely nonsense… has nothing to do with the topic itself and it seems like a attention grabber for views since it’s clearly a over the top scare. But i get it… views = revenue

[cryingwater]

I love IPv6 because my ISP holds me behind a CGNAT so I can't port forward

[bitVanny]

Correction: Windows keeps getting hacked, IPv6 is fine on Linux and Unix. 😊

[JimVajda]

“A critical flaw in IPv6 has just been discovered.” No it hasn’t.

[skid]

Here i thought that maybe it would be something constructive, but no, same thing over and over again from people not understanding the paradigme change about IPv6.

NAT isn't a security feature, the security feature is your firewall that block inbound non-tracked traffic before it gets translated.
So no, IPv6 is not "less secure" than IPv4 as long as you have a properly configured firewall on both sides that do not let non-tracked inbound traffic get in.

The whole video is like "IPv6 is the problem". No, the problem is a vulnerability in the implementation of IPv6 TCP/IP stack by Microsoft on Windows. It's not BECAUSE it's IPv6 related that IPv6 itself is the problem. Like you said, only Windows is vulnerable here.

Also, disabling IPv6 at the OS level is the worst advice you can give, it can break core functions that the OS relies on if you don't know what you're doing. Also by saying that, you just contribute to the slowness of the IPv6 transition with more people saying the same things as i stated before over and over and over again.

Please consider making a corrective video about this.

[bishopdredd]

Do some research and change that title p. You're damaging IPv6 with that headline

[djcmike]

I've switched to IPv6 all over and we are using it at our datacenter too :p But no windows computers, so hey ;)