CVE-2024-38063 - Or, IPv6 fucks everyone again, and still nobody actually uses it

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.

reptile baht spaniard rid

witless witness schema iguanas
True & Honest Fan
kiwifarms.net
Joined
Dec 16, 2019
🚨 PSA: All Windows users should immediately update their computers. An exploit rated 9.8/10 (CVE-2024-38063) compromises all devices running Windows with an IPv6 address.

(archive: https://archive.ph/wMazd )

Windows fags: scream and cry and discuss
Mac fags: smug and laugh and discuss
Linux fags: giggle as you hide 0.0.0.0 and discuss
TempleOS chads: be confirmed in God's righteousness and deny networking as it is of the devil
 
I don't understand this at all. It's RCE through packets?
im retarded, plz explain what this exploit does.
4000 words or less.
Hackers can send fancy ipv6 packets to your machine which, though an integer underflow as the vulnerability mechanism, runs remote code on your machine. This code can install further malware and backdoors.
 
im retarded, plz explain what this exploit does.
4000 words or less.
🚨ChatGPT
The CVE-2024-38063 is a critical vulnerability in Windows TCP/IP, specifically identified as a Remote Code Execution (RCE) vulnerability. This issue affects multiple versions of Windows operating systems, including Windows 10, Windows 11, and several versions of Windows Server, ranging from Server 2008 to Server 2022.

### Key Details:
- **Vulnerability Description:** This vulnerability is related to an integer underflow (CWE-191) in the Windows TCP/IP stack, which could potentially allow an attacker to execute arbitrary code remotely without needing any prior authentication or user interaction.
- **Affected Systems:** Multiple Windows platforms, including various versions of Windows 10, Windows 11, and Windows Server, across 32-bit, x64-based, and ARM64-based systems.
- **Severity:** The vulnerability is rated as **critical** with a CVSS v3.1 base score of 9.8, indicating a high risk of exploitation.
- **Attack Vector:** Network-based, with low attack complexity, no privileges required, and no user interaction necessary. The impact includes complete confidentiality, integrity, and availability loss.

### Mitigation:
Microsoft has released updates to address this vulnerability. It's essential to apply these updates as soon as possible to mitigate the risk of exploitation.

### References:
- [Microsoft Security Response Center (MSRC) Advisory](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-38063)

It's crucial to keep your systems updated to avoid potential exploits targeting this vulnerability.
 
From Microsoft:
Systems are not affected if IPv6 is disabled on the target machine.

Also from Microsoft:

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.

Turning off IPv6 also increases boot time because fuck you
 
FYI disabling ipv6 doesn't seem to work against this vulnerability, since it seems that the attack takes place before your firewall can block ipv6 packets. seems like a problem with the windows ip/tcp stack implementation. Just update.
1723760312392.png

 
FYI disabling ipv6 doesn't seem to work against this vulnerability, since it seems that the attack takes place before your firewall can block ipv6 packets. seems like a problem with the windows ip/tcp stack implementation. Just update.
View attachment 6311747
Seems like if your ISP doesn't support IPv6 or a router filtering it out would stop it. Feel free to correct me if I'm wrong. Still, you should update your shit.
 
Is this new? My organization disabled IPv6 via GPO a couple of months ago for some security problem.
It's from this Tuesday, your org disabled it for other reasons. Often it's a simple "just in case" kinda deal as IPv6 intranets don't really hold any benefits to the absolute vast majority of corpos, 10.0.0.0/8 is a shitload of addresses already and IPv6 often languishes in an unconfigured mess that's better kept shut down to cut down on possible headaches.
 
Is this new? My organization disabled IPv6 via GPO a couple of months ago for some security problem.
They may have received early rumors or notification of it. IPv6 has always been a shitshow, however, and they may have turned it off because it fucks everything up unless setup perfectly.
 
Back