Heap-based buffer overflow in Windows Common Log File System Driver allows an authorized attacker to elevate privileges locally.
Weakness
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| Windows_10_1507 |
Microsoft |
* |
10.0.10240.21034 (excluding) |
| Windows_10_1607 |
Microsoft |
* |
10.0.14393.8148 (excluding) |
| Windows_10_1809 |
Microsoft |
* |
10.0.17763.7434 (excluding) |
| Windows_10_21h2 |
Microsoft |
* |
10.0.19044.5965 (excluding) |
| Windows_10_22h2 |
Microsoft |
* |
10.0.19045.5965 (excluding) |
| Windows_11_22h2 |
Microsoft |
* |
10.0.22621.5472 (excluding) |
| Windows_11_23h2 |
Microsoft |
* |
10.0.22631.5472 (excluding) |
| Windows_11_24h2 |
Microsoft |
* |
10.0.26100.4270 (excluding) |
| Windows_server_2008 |
Microsoft |
–sp2 (including) |
–sp2 (including) |
| Windows_server_2008 |
Microsoft |
r2-sp1 (including) |
r2-sp1 (including) |
| Windows_server_2012 |
Microsoft |
- (including) |
- (including) |
| Windows_server_2012 |
Microsoft |
r2 (including) |
r2 (including) |
| Windows_server_2016 |
Microsoft |
* |
10.0.14393.8148 (excluding) |
| Windows_server_2019 |
Microsoft |
* |
10.0.17763.7434 (excluding) |
| Windows_server_2022 |
Microsoft |
* |
10.0.20348.3745 (excluding) |
| Windows_server_2022_23h2 |
Microsoft |
* |
10.0.25398.1665 (excluding) |
| Windows_server_2025 |
Microsoft |
* |
10.0.26100.4270 (excluding) |
Potential Mitigations
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking.
- D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
- Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.
- Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as “rebasing” (for Windows) and “prelinking” (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking.
- For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].
References