Microsoft OLE DB Driver for SQL Server Remote Code Execution Vulnerability
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 |
Ole_db_driver_for_sql_server |
Microsoft |
18.0.2 (including) |
18.7.0002.0 (excluding) |
Ole_db_driver_for_sql_server |
Microsoft |
19.0.0 (including) |
19.3.0003.0 (excluding) |
Sql_server_2019 |
Microsoft |
15.0.2000.5 (including) |
15.0.2110.4 (excluding) |
Sql_server_2019 |
Microsoft |
15.0.4003.23 (including) |
15.0.4360.2 (excluding) |
Sql_server_2022 |
Microsoft |
16.0.1000.6 (including) |
16.0.1115.1 (excluding) |
Sql_server_2022 |
Microsoft |
16.0.4003.1 (including) |
16.0.4120.1 (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