FFmpeg through 8.1.2, fixed in commit 5d7112c, contains a heap out-of-bounds write vulnerability in the vf_hqdn3d filter that allows attackers to corrupt heap memory by supplying a crafted video whose frame resolution increases between frames when filtergraph reinitialization is disabled via the -reinit_filter 0 option. Attackers can provide a malicious video input where vf_hqdn3d.config_input() allocates undersized per-plane line-history buffers based on the initial frame width, and subsequent larger frames cause denoise_spatial() to write beyond the allocation boundary, resulting in heap memory corruption.
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 |
|---|---|---|---|
| Ffmpeg | Ffmpeg | * | 8.1.2 (including) |
| Red Hat Enterprise Linux AI 3.3 for RHEL 9 | RedHat | ffmpeg-0:6.1.6-7.el9ai | * |
| Red Hat Enterprise Linux AI 3.4 for RHEL 9 | RedHat | ffmpeg-0:6.1.6-7.el9ai | * |
| Red Hat Enterprise Linux AI 3.5 for RHEL 9 | RedHat | ffmpeg-0:6.1.6-7.el9ai | * |
| Red Hat Enterprise Linux AI 3.6 for RHEL 9 | RedHat | ffmpeg-0:6.1.6-8.el9ai | * |
| Red Hat OpenShift AI 2.25 | RedHat | rhoai/odh-vllm-gaudi-rhel9:1786712464 | * |
| Ffmpeg | Ubuntu | esm-apps-legacy/xenial | * |
| Ffmpeg | Ubuntu | esm-apps/bionic | * |
| Ffmpeg | Ubuntu | esm-apps/focal | * |
| Ffmpeg | Ubuntu | esm-apps/jammy | * |
| Ffmpeg | Ubuntu | esm-apps/noble | * |
| Ffmpeg | Ubuntu | esm-apps/resolute | * |
| Ffmpeg | Ubuntu | jammy | * |
| Ffmpeg | Ubuntu | noble | * |
| Ffmpeg | 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].