A flaw was found in rrdcached, a component of rrdtool. A local attacker with access to a rrdcached socket can exploit a stack-based buffer overflow by sending an oversized CREATE request. This vulnerability can lead to a denial of service by crashing the daemon or potentially allow for arbitrary code execution, impacting the integrity and confidentiality of data.
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 |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | RedHat | rrdtool-0:1.8.0-21.el10_2 | * |
| Red Hat Enterprise Linux 8 | RedHat | rrdtool-0:1.7.0-17.el8_10 | * |
| Red Hat Enterprise Linux 9 | RedHat | rrdtool-0:1.7.2-22.el9_8 | * |
| Rrdtool | Ubuntu | devel | * |
| Rrdtool | Ubuntu | esm-infra-legacy/trusty | * |
| Rrdtool | Ubuntu | esm-infra-legacy/xenial | * |
| Rrdtool | Ubuntu | esm-infra/bionic | * |
| Rrdtool | Ubuntu | esm-infra/focal | * |
| Rrdtool | Ubuntu | jammy | * |
| Rrdtool | Ubuntu | noble | * |
| Rrdtool | Ubuntu | questing | * |
| Rrdtool | Ubuntu | resolute | * |
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].