Zero-click Windows TCP/IP RCE impacts all systems with IPv6 enabled, patch now - The thing mentioned in the PSA. Yes, install the patch you fucking idiot

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
Article (bleepingcomputer.com) / Archive

Microsoft warned customers this Tuesday to patch a critical TCP/IP remote code execution (RCE) vulnerability with an increased likelihood of exploitation that impacts all Windows systems using IPv6, which is enabled by default.
Found by Kunlun Lab's XiaoWei and tracked as CVE-2024-38063, this security bug is caused by an Integer Underflow weakness, which attackers could exploit to trigger buffer overflows that can be used to execute arbitrary code on vulnerable Windows 10, Windows 11, and Windows Server systems.
"Considering its harm, I will not disclose more details in the short term," the security researcher tweeted, adding that blocking IPv6 on the local Windows firewall won't block exploits because the vulnerability is triggered prior to it being processed by the firewall.
As Microsoft explained in its Tuesday advisory, unauthenticated attackers can exploit the flaw remotely in low-complexity attacks by repeatedly sending IPv6 packets that include specially crafted packets.
Microsoft also shared its exploitability assessment for this critical vulnerability, tagging it with an "exploitation more likely" label, which means that threat actors could create exploit code to "consistently exploit the flaw in attacks."
"Moreover, Microsoft is aware of past instances of this type of vulnerability being exploited. This would make it an attractive target for attackers, and therefore more likely that exploits could be created," Redmond explains.
"As such, customers who have reviewed the security update and determined its applicability within their environment should treat this with a higher priority."
As a mitigation measure for those who can't immediately install this week's Windows security updates, Microsoft recommends disabling IPv6 to remove the attack surface.
However, on its support website, the company says the IPv6 network protocol stack is a "mandatory part of Windows Vista and Windows Server 2008 and newer versions" and doesn't recommend toggling off IPv6 or its components because this might cause some Windows components to stop working.

Wormable vulnerability​

Head of Threat Awareness at Trend Micro's Zero Day Initiative Dustin Childs also labeled the CVE-2024-38063 bug as one of the most severe vulnerabilities fixed by Microsoft this Patch Tuesday, tagging it as a wormable flaw.
"The worst is likely the bug in TCP/IP that would allow a remote, unauthenticated attacker to get elevated code execution just by sending specially crafted IPv6 packets to an affected target," Childs said.
"That means it's wormable. You can disable IPv6 to prevent this exploit, but IPv6 is enabled by default on just about everything."
While Microsoft and other companies warned Windows users to patch their systems as soon as possible to block potential attacks using CVE-2024-38063 exploits, this isn't the first and likely won't be the last Windows vulnerability exploitable using IPv6 packets.
Over the last four years, Microsoft has patched multiple other IPv6 issues, including two TCP/IP flaws tracked as CVE-2020-16898/9 (also called Ping of Death), that can be exploited in remote code execution (RCE) and denial of service (DoS) attacks using malicious ICMPv6 Router Advertisement packets.
Additionally, an IPv6 fragmentation bug (CVE-2021-24086) left all Windows versions vulnerable to DoS attacks, and a DHCPv6 flaw (CVE-2023-28231) made it possible to gain RCE with a specially crafted call.

Even though attackers are yet to exploit them in widespread attacks targeting all IPv6-enabled Windows devices, users are still advised to apply this month's Windows security updates immediately due to CVE-2024-38063's increased likelihood of exploitation.
 
I don't trust poojeets enough to fix this shit. They likely have caused it with their nepotism, stupidity and general IQ85 retardation in the first place. Seriously, the second the white man was pushed out of IT, everything went to shit.
 
So that's why Windows sent me an update even though they discontinued updates for win 10.
 
You know how 20 years ago, plugging an unpatched system straight into the Internet would clog it with remotely installed viruses within five minutes and zero user input? Once usable attack code starts appearing, this is effectively a return of that golden era.
Is that how the hackers got into Awesomenator's system? Upside is NEETs will have plausible deniability again when their Mom catches them.
 
This kind of bullshit has got to be intentional

Anyone want to translate this shit to someone who is loathed to update their windows due to the bad shit that happens these days if forced to update Windows on their machine?

Nah. Underflows are much less common than their sibling, the overflow, but it's almost a guarantee it's just bad coding. It's a fairly simple mistake to make. You can think of it sort of like like the reverse of the Y2K bug, instead of 1999 rolling over to 1900, it's the reverse, the year is 1900 and you subtract a year, ending up with a date of 1999, instead of 1899. In both example it is a wraparound. One going from the maximum acceptable value to the minimal acceptable value, the other going from the minimal acceptable value all the way to the maximum acceptable value. The first one is also an example of a rollforward, and the other, rollback, both types of what's known as rollover.

In any instance, a good programmer doesn't allow this to happen through any number of methods, but that apparently wasn't done. It's sort of a double fail because one can easily have code in place to handle exceptions and allow for a fail-safe situation, rather than a fail-dangerous situation. So, not only did they not prevent this error, but there was obviously nothing in place to recognize the error and allow the code to fail in an acceptable fashion so as not to create an opportunity for exploitation.

This is all fairly common, these types of things are the origin of what are typically called bugs. Some are just more dangerous than others.
 
Last edited:
It's sort of a double fail because one can easily have code in place to handle exceptions and allow for a fail-safe situation, rather than a fail-dangerous situation. So, not only did they not prevent this error, but there was obviously nothing in place to recognize the error and allow the code to fail in an acceptable fashion so as not to create an opportunity for exploitation.
How do you detect integer overflow/underflow, exactly?

Let's ask PHP devs:
if (integer_value > MAX_INTEGER) then{
...

}
 
Anyone want to translate this shit to someone who is loathed to update their windows due to the bad shit that happens these days if forced to update Windows on their machine?
execute arbitrary code
any time you see a phrase like "arbitrary code execution" or "remote code execution" it means a hacker who knows how to do the exploit has as much access to your computer as someone physically sitting in front of it. they can steal your files, install programs, use the machine for DDoS attacks, mine bitcoin, change your passwords and hold your data for ransom, etc
 
This kind of bullshit has got to be intentional
IPv6 network protocol stack is a "mandatory part of Windows Vista and Windows Server 2008 and newer versions" and doesn't recommend toggling off IPv6 or its components because this might cause some Windows components to stop working.
Does your network not even support IPv6 in the first place? Still gotta enable it, can't have users minimizing attack surface and bloat.
 
I don't trust poojeets enough to fix this shit. They likely have caused it with their nepotism, stupidity and general IQ85 retardation in the first place. Seriously, the second the white man was pushed out of IT, everything went to shit.
This bug has existed since msft introduced ipv6. I think it exists back to nt/me. I think it has been confirmed back to xp.

So can't blame the poojeets for this.

Also I think you can't even disable ipv6 to stop this. You can get to the loop back address even with v6 disabled. Try ""ping ::1" with v6 disabled.

This could be used for local priv escalation.

I have been wondering when we would see an exploit causing older windows to need to get retired. They had been pretty stable running 2003/xp for a while.
 
Back
Top Bottom