CVE-2016-4352
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 · uneditedInteger overflow in the demuxer function in libmpdemux/demux_gif.c in Mplayer allows remote attackers to cause a denial of service (crash) via large dimensions in a gif 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 · high confidenceInteger overflow in the GIF demuxer (demux_gif.c) in MPlayer allows remote attackers to cause a denial of service by providing a GIF file with excessively large dimensions that overflow integer calculations.
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<= 57.34.103CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 if MPlayer or Libavformat is installedRun 'mplayer -version' or check for libavformat library files (e.g., libavformat.so*) in system directories like /usr/libAffected if Either MPlayer or Libavformat library is present on the system
-
Determine the installed Libavformat versionRun 'ffprobe -version' or 'avprobe -version' to display version information, or use 'ldd' on MPlayer to see linked libavformat versionAffected if The reported Libavformat version is 57.34.103 or earlier (any version <= 57.34.103)
-
Verify the GIF demuxer module existsCheck for the demux_gif.c compiled module or the presence of GIF support in MPlayer/Libavformat by examining installed codec/filter directories or running 'mplayer -demuxer help' 2>/dev/null | grep -i gifAffected if GIF demuxer is available and can be invoked when opening a GIF file
-
Confirm GIF file processing is possibleAttempt to open any GIF file with MPlayer or ffprobe (e.g., 'mplayer -vo null -ao null sample.gif' or 'ffprobe sample.gif'), or check if libavformat is linked to an application that processes user-supplied GIF filesAffected if The system can parse and demux GIF files using the vulnerable Libavformat code path
The system is affected if Libavformat version 57.34.103 or earlier is installed and the GIF demuxer is accessible to process files.
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 dataUpdate MPlayer to a version that includes bounds checking on GIF dimension values before performing integer arithmetic, or apply the relevant patch that adds validation of width/height parameters.
- Consultation4.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,024.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-4352 — 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-4352 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