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

  • 🏰 The Fediverse is up. If you know, you know.
  • 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.
 
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?
 
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?
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.
 
Win 7 bros stay winning.
This is being patched for Windows Server 2008R2 which is the serverized version of Win7, and even straight 2008 which is based on Vista. You're absolutely on the firing line, except Microsoft didn't apparently deem the consumer version worth patching.
 
IPv6 has been such a fucking mistake. I frantically studied it back like a decade ago when all the news was "We've run out of IPv4 addresses!" Never used it once since. Every company I've done any work for has been steadfastly on IPv4 and toggles off the IPv6 settings on their stuff ASAP.
 
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?
Translation: I can connect to your computer using IPv6 which isn't that common but Windows enables it by default out of the box. How isn't important, it's just important that I send something and the computer responds, I will tell you that it's trivial to setup though, I can make something to connect this way in about 10 minutes and there are tools out there that do it for you that eliminates the need to program your own tools altogether.

Once that's done, I can proceed to feed your computer the right type and amount of data in such a way that it just shrugs and lets you run whatever command you want, which means I own the entire computer. What good is any of the other security stuff if I can trick it into giving me all of the access I need to create another account or access whatever I want without having to log in. You can do this over a local network or over the internet. Internet is harder, but not impossible. IPv6 also isn't used nearly as often, but mobile networks often hand out IPv6 addresses and some ISPs do as well. Whether you can hit a computer over the internet or on a local network with IPv6 is hit and miss, depends on the network you're connected to. If you've got an IPv6 address assigned to your computer and someone can connect to it, you're fucked.

The only good news is that it appears to be only IPv6, if it was IPv4 which is what you'll have no matter what and use most of the time, this would be much worse.

If there was ever a reason to install an update for your computer, this would be it. It's not about whether something will happen right now, it's when there's a repeatable process to exploit this vulnerability that any script kiddie can pick up on the internet months to years from now that's the real problem.

This is being patched for Windows Server 2008R2 which is the serverized version of Win7, and even straight 2008
I didn't even see that. If microsoft is backporting a patch to 2008 then it's pretty fucking bad. Normally they'd jump at the chance to charge you obscene amounts of money for security patches to old server OSs. The fact that they're giving this one away for free speaks volumes.
 
Last edited:
I didn't even see that. If microsoft is backporting a patch to 2008 then it's pretty fucking bad. Normally they'd jump at the chance to charge you obscene amounts of money for security patches to old server OSs. The fact that they're giving this one away for free speaks volumes.
I looked it up and apparently it's grandfathered support contracts, MS managed to get themselves stuck in deals that obligate them to provide 2008/R2 support all the way to fucking 2026.
 
I looked it up and apparently it's grandfathered support contracts, MS managed to get themselves stuck in deals that obligate them to provide 2008/R2 support all the way to fucking 2026.
That makes more sense, their default response in this situation is typically "fuck you, pay me". Maybe that's why they make the OS progressively shittier and shitter with every release, it encourages technical debt and fuels a revenue stream. That's just my autism-fueled schizo conspiracy theory.
big-thunk..:thinking:
 
Back
Top Bottom