News for hackers. Stuff that matters.
Re:Windows TCP/IP Remote Code Execution Vulnerability by yyyk on Wednesday August 14, 2024 @08:09AM (#41245138)
Every Windows-based business LAN or industrial machine I know still has IPv6 disabled. Most other targets are too low value for people to bother.
Re:Windows TCP/IP Remote Code Execution Vulnerability by toast0 on Wednesday August 14, 2024 @10:55AM (#41246829)
IPv6 actually disabled or meerly inactive because there's no router advertisements on the LAN?

I suspect more of the second than the first. If it's just inactive, a compromised host can often broadcast a router advertisement or perhaps use local net addresses to compromise other hosts. A well prepared network would block ipv6 traffic on their switches, it they don't want it, but that's a big investment in capable switches.

Re:Windows TCP/IP Remote Code Execution Vulnerability by GoblinSlayer on Wednesday August 14, 2024 @11:06AM (#41246979)
Re:Windows TCP/IP Remote Code Execution Vulnerability by dogsledsleddog on Wednesday August 14, 2024 @05:15PM (#41250587)
Which says:

> You cannot completely disable IPv6 as IPv6 is used internally on the system for many TCPIP tasks. For example, you will still be able to run ping ::1 after configuring this setting.

I'd be concerned their workaround is just limiting it into a local vulnerability that spyware, etc will abuse on all the systems that end up not patched because they used the workaround..

Re:Windows TCP/IP Remote Code Execution Vulnerability by GoblinSlayer on Thursday August 15, 2024 @03:53AM (#41253917)
When spyware holds your ass, it already has everything on you and doesn't need any vulnerability.
Re:Windows TCP/IP Remote Code Execution Vulnerability by IcePic on Thursday August 15, 2024 @04:03AM (#41253955)
> When spyware holds your ass, it already has everything on you and doesn't need any vulnerability.

..because it uses one of the available local escalation tricks, where sending RA to ::1 could be one of those if that is a thing.

Re:Windows TCP/IP Remote Code Execution Vulnerability by yyyk on Wednesday August 14, 2024 @12:02PM (#41247583)
I mean 'disabled in network adapter connection properties'. If you're already using IPv4 there's no reason for the extra complications of leaving IPv6 enabled.
Re:Windows TCP/IP Remote Code Execution Vulnerability by sgjohnson on Wednesday August 14, 2024 @01:49PM (#41248695)
> If you're already using IPv4 there's no reason for the extra complications of leaving IPv6 enabled.

That’s just flat out wrong. No pure IPv6 deployments exist on endpoints in practice. Only in internal networks. You either run pure v4, or dual stacked v4+v6.

IPv6 is gaining some pretty solid adoption these days, but it’s not there yet. Disabling it is holding back the deployment of it, and is a problem by itself.

Re:Windows TCP/IP Remote Code Execution Vulnerability by yyyk on Wednesday August 14, 2024 @01:59PM (#41248802)
The context ('business LAN or industrial machine') referred to internal networks. What happened there doesn't really effect IPv6 adoption.
Re:Windows TCP/IP Remote Code Execution Vulnerability by orev on Wednesday August 14, 2024 @11:44AM (#41247400)
That’s definitely not the norm. IPv6 is enabled by default and it’s not recommended to disable it. Only really locked down places that are ignoring recommendations would have it disabled.

Whether it’s exposed to the Internet is another question, but pretty much everyone has a firewall to at least stop passive scans.

Re:Windows TCP/IP Remote Code Execution Vulnerability by doubleg72 on Wednesday August 14, 2024 @10:12PM (#41252555)
We do it in our 10k+ environment.
Re:Windows TCP/IP Remote Code Execution Vulnerability by ammo1662 on Thursday August 15, 2024 @02:11AM (#41253507)
It seems that this can be triggered before the packet reaches the firewall.

https://www.bleepingcomputer.com/news/microsoft/zero-click-w...

Re:Windows TCP/IP Remote Code Execution Vulnerability by orev on Thursday August 15, 2024 @02:07PM (#41258796)
I meant a network level firewall at the perimeter, but this is good information to know you can’t rely on the Windows firewall.
Re:Windows TCP/IP Remote Code Execution Vulnerability by throw0101c on Wednesday August 14, 2024 @04:09PM (#41249993)
> Every Windows-based business LAN or industrial machine I know still has IPv6 disabled.

Which is against Microsoft's recommendations:

> Internet Protocol version 6 (IPv6) is a mandatory part of Windows Vista and Windows Server 2008 and newer versions. We do not recommend that you disable IPv6 or its components. If you do, some Windows components may not function.

* https://learn.microsoft.com/en-us/troubleshoot/windows-serve...

Re:Windows TCP/IP Remote Code Execution Vulnerability by olyjohn on Wednesday August 14, 2024 @05:47PM (#41250845)
Microsoft doesn't even listen to their own recommendations. Why would anybody else?