CVE-2016-9447
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 ROM mappings in the NSF decoder in gstreamer 0.10.x allow remote attackers to cause a denial of service (out-of-bounds read or write) and possibly execute arbitrary code via a crafted NSF music file.
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 · moderate confidenceThe vulnerability exists in the NSF (NES Sound Format) decoder plugin in GStreamer 0.10.x. The ROM mappings in the decoder lack proper bounds checking when parsing NSF files, allowing an out-of-bounds read or write when processing a specially crafted file. This can cause denial of service and potentially allow arbitrary code execution.
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= 0.10.0= 0.10.1= 0.10.2= 0.10.3= 0.10.4= 0.10.5= 0.10.6= 0.10.7= 0.10.8= 0.10.9= 0.10.10= 0.10.11CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 GStreamer versionRun 'gst-inspect-0.10 --version' or check package manager for gstreamer0.10-base versionAffected if Version is 0.10.0 through 0.10.11 (any 0.10.x release)
-
Locate NSF decoder pluginRun 'gst-inspect-0.10 nsf' or search for libgstnsf.so in plugin directories (typically /usr/lib/gstreamer-0.10/)Affected if The NSF decoder plugin (nsf) is installed and available
-
Verify plugin loads without errorRun 'gst-launch-0.10 --version' and attempt 'gst-inspect-0.10 nsf' to confirm plugin is functionalAffected if Plugin loads successfully - meaning the vulnerable code path exists in your environment
-
Confirm NSF file processing capabilityCheck if applications using GStreamer 0.10 can load NSF files (test with gst-launch-0.10 filesrc location=file.nsf ! nsfdec ! fakesink)Affected if NSF files can be decoded - the vulnerable code path is reachable
You are affected if GStreamer 0.10.x is installed with the NSF decoder plugin and you process NSF files, particularly from untrusted sources.
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 dataApply the vendor-supplied patch to GStreamer 0.10.x to fix the NSF decoder bounds checking issue. Until patched, avoid processing NSF files from untrusted sources.
- 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-9447 — 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-9447 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