News for hackers. Stuff that matters.
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.