VYPR
Unrated severityNVD Advisory· Published Sep 20, 2021· Updated Aug 3, 2024

CVE-2021-32278

CVE-2021-32278

Description

A heap-buffer-overflow in faad2's lt_prediction function allows remote code execution via crafted AAC files.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A heap-buffer-overflow in faad2's lt_prediction function allows remote code execution via crafted AAC files.

Vulnerability

A heap-buffer-overflow vulnerability exists in the lt_prediction function in lt_predict.c at line 108. The issue affects faad2 through version 2.10.0 and was confirmed on the latest master commit (f71b5e) at the time of disclosure [1]. The overflow occurs when processing a specially crafted AAC file, specifically during the reconstruction of a single channel in the spectral data decoding phase [1].

Exploitation

An attacker can trigger the vulnerability by supplying a malicious AAC file to the faad2 decoder. The provided reference demonstrates a proof of concept using the command ./frontend/faad -w -b 5 @@ on an Ubuntu x86_64 system compiled with AddressSanitizer [1]. No special privileges or user interaction beyond opening the file are required; the overflow is triggered during normal decoding as the file is parsed through faad_main --> decodeMP4file --> aac_frame_decode --> raw_data_block --> decode_sce_lfe --> reconstruct_single_channel --> lt_prediction [1].

Impact

Successful exploitation results in a heap-buffer-overflow read of size 2 bytes at a memory location 122 bytes to the left of an allocated region [1]. While the crash is a read overflow, the context of a heap overflow can be leveraged by an attacker to achieve code execution, as indicated in the official description of the CVE. The attacker gains the ability to execute arbitrary code with the privileges of the process running the faad2 decoder.

Mitigation

As of the publication date (2021-09-20), no official patch has been released for this vulnerability [1]. Users are advised to monitor the faad2 repository for updates and avoid processing untrusted AAC files with affected versions (<= 2.10.0). The issue is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog as of this writing.

AI Insight generated on May 27, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

Root cause

"Missing bounds check in lt_prediction allows reading past the allocated heap buffer when processing a crafted AAC LFE channel element."

Attack vector

An attacker supplies a crafted AAC file that triggers a heap-buffer-overflow read in `lt_prediction` at `lt_predict.c:108` [ref_id=1]. The overflow occurs when the decoder processes an LFE (low-frequency effects) channel element, reading 2 bytes from a heap buffer at an offset 122 bytes before the allocated region. No authentication or special network access is required beyond delivering the malformed file to the faad2 decoder.

Affected code

The heap-buffer-overflow occurs in the function `lt_prediction` located in `libfaad/lt_predict.c` at line 108. The call chain proceeds through `reconstruct_single_channel` in `specrec.c`, `single_lfe_channel_element` and `decode_sce_lfe` in `syntax.c`, and ultimately `aac_frame_decode` in `decoder.c`.

What the fix does

The advisory does not include a patch. The issue was reported against faad2 up to version 2.10.0, and the repository commit history would need to be inspected for a fix. Without a published patch, the remediation guidance is to avoid processing untrusted AAC files with the affected versions until a fix is applied.

Preconditions

  • inputThe attacker must supply a crafted AAC file that triggers the LFE channel decoding path.
  • configThe victim must run the faad2 decoder (e.g., the `faad` frontend) on the crafted file.

Generated on May 29, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.

References

3

News mentions

0

No linked articles in our index yet.