CVE-2024-47775

What it actually does

Out-of-bounds read in parse_ds64 within gstwavparse.c due to missing buffer length validation before multiple GST_READ_UINT32_LE operations, allowing reads past allocated data.

Why it matters to the business

Applications handling untrusted media files may crash or expose memory contents, disrupting media processing workflows and risking sensitive data exposure in environments relying on GStreamer for audio/video handling.

How an attack unfolds

An attacker crafts a malformed WAV file with a ds64 chunk smaller than expected; when GStreamer parses the file the parse_ds64 function performs unchecked reads, resulting in memory disclosure or process termination.

How to fix it

Upgrade GStreamer to version 1.24.10 or apply commit 5be4b6f03689ab438822f6cfcd13f1f300afe203 in the gstreamer repository.

How to confirm the fix worked

Confirm installed GStreamer version is at least 1.24.10; test parsing of boundary-case WAV files to verify no crash or unexpected memory access occurs.

Typical attack path

1. Attacker supplies a specially crafted WAV file to a target application
2. Application invokes GStreamer's WAV parser on the file
3. parse_ds64 reads beyond buffer bounds without validation
4. Process crashes or leaks adjacent memory contents

How to detect it

Review application logs and crash reports for segmentation faults or memory access violations during WAV parsing; correlate with file ingestion timestamps.

What your security team should do

• Apply the 1.24.10 update or equivalent commit immediately on all systems processing media
• Restrict processing of untrusted WAV files until patched
• Monitor for GStreamer-related crashes in media-handling services
• Review downstream dependents for inherited exposure