CVE-2016-9812
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe gst_mpegts_section_new function in the mpegts decoder in GStreamer before 1.10.2 allows remote attackers to cause a denial of service (out-of-bounds read) via a too small section.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe gst_mpegts_section_new function in GStreamer's MPEG-TS decoder lacks proper bounds validation when processing section data, allowing an out-of-bounds read when a specially crafted (too small) MPEG-TS section is parsed. This causes a denial of service via memory access violation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.10.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed GStreamer core versionRun 'gst-inspect-1.0 --version' or check the package manager (dpkg -l libgstreamer1.0-0, rpm -q gstreamer1, etc.)Affected if Version is 1.10.1 or earlier (any release up to and including 1.10.1)
-
Determine if MPEG-TS demux plugin is availableRun 'gst-inspect-1.0 mpegtsdemux' to confirm the mpegtsdemux element is installed and note its version info if displayedAffected if The mpegtsdemux element is present in the GStreamer installation
-
Check for active MPEG-TS parsing in running pipelinesInspect any running GStreamer pipelines or applications that process MPEG-TS (transport stream) content - look for pipelines containing 'mpegtsdemux' or files with .ts extension being processedAffected if A pipeline is actively parsing MPEG-TS sections using the vulnerable code path
-
Identify applications using libgstreamer for MPEG-TS processingReview logs, running processes, or application configurations for software that parses MPEG-TS streams (common in media players, streaming servers, broadcast tools)Affected if Any application is processing MPEG-TS sections through GStreamer
You are affected if GStreamer version is 1.10.1 or earlier AND the mpegtsdemux module is being used to parse MPEG-TS section data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade GStreamer to version 1.10.2 or later which contains the bounds checking fix; alternatively, apply the upstream patch to add section size validation before dereferencing.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-9812 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-9812 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data