Stack-based buffer overflow in .NET Framework allows an unauthorized attacker to deny service over a network.
Weakness
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| .net_framework | Microsoft | 4.8 (including) | 4.8 (including) |
| Red Hat Enterprise Linux 10 | RedHat | dotnet8.0-0:8.0.129-1.el10_2 | * |
| Red Hat Enterprise Linux 10 | RedHat | dotnet9.0-0:9.0.119-1.el10_2 | * |
| Red Hat Enterprise Linux 10 | RedHat | dotnet10.0-0:10.0.110-1.el10_2 | * |
| Red Hat Enterprise Linux 8 | RedHat | dotnet9.0-0:9.0.119-1.el8_10 | * |
| Red Hat Enterprise Linux 8 | RedHat | dotnet10.0-0:10.0.110-1.el8_10 | * |
| Red Hat Enterprise Linux 8 | RedHat | dotnet8.0-0:8.0.129-1.el8_10 | * |
| Red Hat Enterprise Linux 9 | RedHat | dotnet8.0-0:8.0.129-1.el9_8 | * |
| Red Hat Enterprise Linux 9 | RedHat | dotnet9.0-0:9.0.119-1.el9_8 | * |
| Red Hat Enterprise Linux 9 | RedHat | dotnet10.0-0:10.0.110-1.el9_8 | * |
| Red Hat Hardened Images | RedHat | dotnet10-0-main-10.0.109-1.hum1 | * |
| Red Hat Hardened Images | RedHat | dotnet9-0-main-9.0.118-1.hum1 | * |
| Red Hat Hardened Images | RedHat | dotnet8-0-main-8.0.129-2.1.hum1 | * |
| Dotnet10 | Ubuntu | devel | * |
| Dotnet10 | Ubuntu | noble | * |
| Dotnet10 | Ubuntu | resolute | * |
| Dotnet7 | Ubuntu | jammy | * |
| Dotnet8 | Ubuntu | jammy | * |
| Dotnet8 | Ubuntu | noble | * |
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].