CVE-2016-10198

What it actually does

Invalid memory read in the AAC parser sink caps handler triggers a process crash when processing malformed input.

Why it matters to the business

Media-processing pipelines or applications that ingest untrusted audio can be forced offline, causing service interruption; the issue affects a small number of downstream packages and has been resolved in an updated release.

How an attack unfolds

An attacker supplies a specially crafted AAC audio file to any application using the vulnerable GStreamer parser; the gst_aac_parse_sink_setcaps function performs an out-of-bounds read and aborts, resulting in denial of service.

How to fix it

Upgrade calico-fips-3.25 to version 3.25.2-r7 or later; rebuild any containers or images that embed the affected gst-plugins-good package.

How to confirm the fix worked

Confirm the installed GStreamer version is 1.10.3 or newer; run regression tests with known-malformed AAC samples to verify the crash no longer occurs.

Typical attack path

1. Identify an application or service that uses GStreamer to parse AAC audio
2. Craft or obtain a malicious audio file that triggers the vulnerable caps handler
3. Deliver the file through normal ingestion channels (upload, stream, or file drop)
4. Trigger parsing so the sink caps function executes on the malformed data
5. Observe process crash and service unavailability

How to detect it

Review application or container logs for segmentation faults or GStreamer parser errors immediately after AAC file ingestion; correlate crash timestamps with file-upload or streaming events.

What your security team should do

• Apply the fixed package version immediately in build pipelines
• Inventory all images and deployments that depend on the vulnerable gst-plugins-good library
• Add automated version checks for GStreamer components to CI/CD gates