August 16th, 2024

Zero-click Windows TCP/IP RCE impacts all systems with IPv6 enabled, patch now

Microsoft warns of a critical TCP/IP vulnerability (CVE-2024-38063) affecting all IPv6-enabled Windows systems, allowing remote code execution. Users should prioritize patching to mitigate risks, as the exploit is wormable.

Read original articleLink Icon
Zero-click Windows TCP/IP RCE impacts all systems with IPv6 enabled, patch now

Microsoft has issued a warning regarding a critical TCP/IP remote code execution (RCE) vulnerability, tracked as CVE-2024-38063, affecting all Windows systems with IPv6 enabled. This vulnerability, identified by Kunlun Lab, stems from an Integer Underflow weakness that could allow attackers to execute arbitrary code by sending specially crafted IPv6 packets. Microsoft has labeled the exploit as "more likely," indicating a high risk of exploitation. Users are advised to prioritize patching their systems to mitigate potential attacks. Although disabling IPv6 could reduce the attack surface, Microsoft cautions against this as it may disrupt essential Windows components. The vulnerability is considered wormable, meaning it could be exploited without user interaction. This is not the first instance of such vulnerabilities in Windows, as several others have been patched in recent years, highlighting a persistent security concern with IPv6. Users are urged to apply the latest security updates immediately to protect against this and similar vulnerabilities.

- Microsoft warns of a critical RCE vulnerability (CVE-2024-38063) affecting all IPv6-enabled Windows systems.

- The vulnerability allows remote code execution via specially crafted IPv6 packets.

- Users are advised to prioritize patching their systems to mitigate risks.

- Disabling IPv6 is not recommended as it may disrupt Windows functionality.

- The vulnerability is classified as wormable, increasing the urgency for updates.

Related

Windows: Insecure by Design

Windows: Insecure by Design

Ongoing security issues in Microsoft Windows include vulnerabilities like CVE-2024-30080 and CVE-2024-30078, criticized for potential remote code execution. Concerns raised about privacy with Recall feature, Windows 11 setup, and OneDrive integration. Advocacy for Linux desktops due to security and privacy frustrations.

Hackers bypass Windows SmartScreen flaw to launch malware

Hackers bypass Windows SmartScreen flaw to launch malware

Cybercriminals are exploiting a Microsoft Defender vulnerability (CVE-2024-21412) to install malware undetected. Many systems remain unpatched, making them vulnerable. Users should update Windows and be cautious with email attachments.

Microsoft calls for Windows changes and resilience after CrowdStrike outage

Microsoft calls for Windows changes and resilience after CrowdStrike outage

Microsoft is reconsidering security vendor access to the Windows kernel after a CrowdStrike update outage affected 8.5 million PCs, emphasizing the need for improved resilience and collaboration in security practices.

The Wild West of Proof of Concept Exploit Code (PoC)

The Wild West of Proof of Concept Exploit Code (PoC)

CVE-2024-6387 is a serious unauthenticated remote code execution vulnerability in OpenSSH, with complex exploitation requiring knowledge of system architecture. The exploit code contains malicious elements, emphasizing risks of untrusted code.

Mac and Windows users infected by software updates delivered over hacked ISP

Mac and Windows users infected by software updates delivered over hacked ISP

Hackers compromised an ISP to deliver malware to Windows and Mac users via software updates, affecting multiple applications. Users are advised to avoid insecure updates and use secure DNS protocols.

Link Icon 10 comments
By @ajdude - 5 months

    > 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.
This is pretty nasty.
By @jiggawatts - 5 months
In this thread: luddites congratulating themselves that their routine of setting up a new PC by disabling IPv6, turning off JavaScript, and setting the terminal to green FixedSys has finally paid off.
By @freddierest - 5 months
This will justifiably be used to disable IPv6 in many places, which will sadly set back IPv6 adoption just that little bit more.

I'm IPv6-only on my personal infra, and it's pretty nice. End to end reachability between machines and containers, and reduced need for middle boxes like reverse proxies.

By @hi-v-rocknroll - 5 months
Microsoft product quality déjà vu c. 1990's. If a vendor is going to build and maintain a wide-used operating system, at least they should take the trouble to thoroughly test it, use safer and consistent SWE practices, and use formal verification processes to prove artifacts created fulfill a desired behavior model without deleterious or undesirable side-effects. But no, there is no accountability and certain vendors continue to do the same thing and expect a different result. Customers maybe left to find alternatives rather than continue the stupidity and/or insanity, of which there aren't meaningfully better alternatives, and so running systems becomes a Hobson's choice between use and nothing.
By @londons_explore - 5 months
What's the betting that next week someone deploys a worm using this attack to immediately get tens of millions of windows PC's under their control?

The only real defence is that ipv6 addresses are harder to guess.

By @exabrial - 5 months
I would recommend just disabling ipv6 completely. There is zero need for every machine on the internet to be able to know your computer exists. 15 years ago I had a different opinion, I thought the technology was superior and really well thought out. Today, when Silicon Valley wholesale selling your personal life away for advertisers, I recommend doing the exact opposite of whatever they tell you to do. In this case, those pushing ipv6 the hardest are the Googles/Facebooks/etc.
By @ChrisArchitect - 5 months
By @BenjiWiebe - 5 months
I wonder if most/any routers will allow the bad packets through to the Windows PC?

I'd assume it's probably blocked by the vast majority if it's a TCP vuln (cause stateful firewalls).

By @dmitrygr - 5 months
Safe for all those of us who start a new windows config by disabling IPv6. Most machines are thus probably safe.
By @HereIGoAgain - 5 months
IPv6 has been disabled at the adapter level on my system for years. Or does it have to be reg edit and all too?