CVE-2024-43641
published 2024-11-12CVE-2024-43641: Windows Registry Elevation of Privilege Vulnerability
high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
Windows Registry Elevation of Privilege Vulnerability
Affected
47 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| microsoft | windows_10_1507 | < 10.0.10240.20826 | 10.0.10240.20826 |
| microsoft | windows_10_1607 | < 10.0.14393.7515 | 10.0.14393.7515 |
| microsoft | windows_10_1809 | < 10.0.17763.6532 | 10.0.17763.6532 |
| microsoft | windows_10_21h2 | < 10.0.19044.5131 | 10.0.19044.5131 |
| microsoft | windows_10_22h2 | < 10.0.19045.5131 | 10.0.19045.5131 |
| microsoft | windows_10_version_1507 | >= 10.0.10240.0 < 10.0.10240.20826 | 10.0.10240.20826 |
| microsoft | windows_10_version_1607 | >= 10.0.14393.0 < 10.0.14393.7515 | 10.0.14393.7515 |
| microsoft | windows_10_version_1809 | >= 10.0.17763.0 < 10.0.17763.6532 | 10.0.17763.6532 |
| microsoft | windows_10_version_21h2 | >= 10.0.19043.0 < 10.0.19044.5131 | 10.0.19044.5131 |
| microsoft | windows_10_version_22h2 | >= 10.0.19045.0 < 10.0.19045.5131 | 10.0.19045.5131 |
| microsoft | windows_11_22h2 | < 10.0.22621.4460 | 10.0.22621.4460 |
| microsoft | windows_11_23h2 | < 10.0.22631.4460 | 10.0.22631.4460 |
| microsoft | windows_11_24h2 | < 10.0.26100.2314 | 10.0.26100.2314 |
| microsoft | windows_11_version_22h2 | >= 10.0.22621.0 < 10.0.22621.4460 | 10.0.22621.4460 |
| microsoft | windows_11_version_22h3 | >= 10.0.22631.0 < 10.0.22631.4460 | 10.0.22631.4460 |
| microsoft | windows_11_version_23h2 | >= 10.0.22631.0 < 10.0.22631.4460 | 10.0.22631.4460 |
| microsoft | windows_11_version_24h2 | >= 10.0.26100.0 < 10.0.26100.2314 | 10.0.26100.2314 |
| microsoft | windows_server_2008 | — | — |
| microsoft | windows_server_2008_r2_service_pack_1 | >= 6.1.7601.0 < 6.1.7601.27415 | 6.1.7601.27415 |
| microsoft | windows_server_2008_service_pack_2 | >= 6.0.6003.0 < 6.0.6003.22966 | 6.0.6003.22966 |
| microsoft | windows_server_2012 | — | — |
| microsoft | windows_server_2012 | >= 6.2.9200.0 < 6.2.9200.25165 | 6.2.9200.25165 |
| microsoft | windows_server_2012_r2 | >= 6.3.9600.0 < 6.3.9600.22267 | 6.3.9600.22267 |
| microsoft | windows_server_2016 | < 10.0.14393.7515 | 10.0.14393.7515 |
| microsoft | windows_server_2016 | >= 10.0.14393.0 < 10.0.14393.7515 | 10.0.14393.7515 |
Microsoft
Windows Registry Elevation of Privilege Vulnerability
vendor_msrc·2024-11-12·CVSS 7.8
CVE-2024-43641 [HIGH] CWE-190 Windows Registry Elevation of Privilege Vulnerability
Windows Registry Elevation of Privilege Vulnerability
FAQ: What privileges could be gained by an attacker who successfully exploited this vulnerability?
An attacker who successfully exploited this vulnerability could gain SYSTEM privileges.
Windows Registry: Windows Registry
Microsoft: Microsoft
Customer Action Required: Yes
Impact: Elevation of Privilege
Exploit Status: Publicly Disclosed:No;Exploited:No;Latest Software Release:Exploitation Less Likely
Reference: https://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5046617
Reference: https://support.microsoft.com/help/5046617
Reference: https://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5046696
Reference: https://support.microsoft.com/help/5046696
Reference: https://catalog.update.microsoft.com/v7/site/Search.
Project0
The Windows Registry Adventure #7: Attack surface analysis - Project Zero
project_zero·2025-05-01
CVE-2010-0237 The Windows Registry Adventure #7: Attack surface analysis - Project Zero
Posted by Mateusz Jurczyk, Google Project Zero
In the first three blog posts of this series, I sought to outline what the Windows Registry actually is, its role, history, and where to find further information about it. In the subsequent three posts, my goal was to describe in detail how this mechanism works internally – from the perspective of its clients (e.g., user-mode applications running on Windows), the regf format used to encode hives, and finally the kernel itself, which contains its canonical implementation. I believe all these elements are essential for painting a complete picture of this subsystem, and in a way, it shows my own approach to security research. One could say that going through this tedious process of getting to know the target unnecessarily lengthens the total
Project0
The Windows Registry Adventure #5: The regf file format - Project Zero
project_zero·2024-12-01
CVE-2015-0073 The Windows Registry Adventure #5: The regf file format - Project Zero
Posted by Mateusz Jurczyk, Google Project Zero
As previously mentioned in the second installment of the blog post series ("A brief history of the feature"), the binary format used to encode registry hives from Windows NT 3.1 up to the modern Windows 11 is called regf. In a way, it is quite special, because it represents a registry subtree simultaneously on disk and in memory, as opposed to most other common file formats. Documents, images, videos, etc. are generally designed to store data efficiently on disk, and they are subsequently parsed to and from different in-memory representations whenever they are read or written. This seems only natural, as offline storage and RAM come with different constraints and requirements. On disk, it is important that the data is packed as tightly as
GHSA
GHSA-693v-cgfp-qgfp: Windows Registry Elevation of Privilege Vulnerability
ghsa_unreviewed·2024-11-12
CVE-2024-43641 [HIGH] CWE-190 GHSA-693v-cgfp-qgfp: Windows Registry Elevation of Privilege Vulnerability
Windows Registry Elevation of Privilege Vulnerability
No detection rules found.
No public exploits indexed.
2024-11-12
Published