CVE-2024-47615

What it actually does

Out-of-bounds write in gst_parse_vorbis_setup_packet where an unvalidated integer size from the input exceeds the 256-element vorbis_mode_sizes array, causing a loop to overwrite the containing pad structure and up to 380 bytes of adjacent memory with attacker-controlled 0/1 values.

Why it matters to the business

Media-processing applications and pipelines that ingest untrusted Vorbis streams can be crashed or compromised, leading to service outages or arbitrary code execution on systems that rely on GStreamer for audio/video handling.

How an attack unfolds

An attacker supplies a crafted Vorbis setup packet containing an oversized size field; when the parser reads this value without bounds checking and enters the overwrite loop, memory corruption occurs that can be leveraged for control-flow hijacking or denial of service.

How to fix it

Upgrade gstreamer to version 1.24.10 or later; the fix is present in commit 5be4b6f03689ab438822f6cfcd13f1f300afe203. Rebuild any dependent packages and restart affected pipelines after the update.

How to confirm the fix worked

Confirm the installed GStreamer version reports 1.24.10 or newer; run regression tests that feed the previously crashing vorbis setup packet and verify the process no longer writes beyond the array bounds.

Typical attack path

1. Attacker crafts malicious Vorbis media containing oversized vorbis setup packet
2. Target application opens or streams the malicious file through GStreamer
3. vorbis_parse.c gst_parse_vorbis_setup_packet reads the unchecked size value
4. For-loop overwrites pad structure and adjacent memory
5. Resulting corruption enables code execution or crash

How to detect it

Review application and system logs for segmentation faults or memory-corruption signals occurring during Vorbis parsing; correlate crashes with inbound media files that contain vorbis setup packets.

What your security team should do

• Immediately update all GStreamer installations to 1.24.10 or the commit 5be4b6f
• Scan build pipelines and containers for older GStreamer versions and rebuild them
• Add the fixed version constraint to dependency manifests and CI enforcement rules
• Monitor for any downstream projects that embed vulnerable GStreamer copies