CVE-2016-2328
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 · uneditedlibswscale/swscale_unscaled.c in FFmpeg before 2.8.6 does not validate certain height values, which allows remote attackers to cause a denial of service (out-of-bounds array read access) or possibly have unspecified other impact via a crafted .cine file, related to the bayer_to_rgb24_wrapper and bayer_to_yv12_wrapper functions.
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 confidenceA height validation vulnerability exists in FFmpeg's libswscale component (swscale_unscaled.c) before version 2.8.6. The bayer_to_rgb24_wrapper and bayer_to_yv12_wrapper functions fail to validate height values when processing Bayer format images from .cine files, allowing out-of-bounds array read access. This can cause denial of service via memory read beyond allocated buffers, and may permit unspecified other impact potentially including 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<= 2.8.5CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/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 installed FFmpeg versionRun `ffmpeg -version` or check the libswscale library file version (e.g., `pkg-config --modversion libswscale` or inspect the shared object file)Affected if Version is 2.8.5 or lower (any version <= 2.8.5)
-
Confirm .cine file processing is in useReview application logs, source code, or runtime environment to determine whether .cine (Cineon) image files are being decoded or processed by FFmpegAffected if The system processes .cine format files from untrusted sources
-
Verify Bayer format decoding is invokedCheck if bayer_to_rgb24_wrapper or bayer_to_yv12_wrapper functions are called by examining processed file metadata, using verbose FFmpeg logging (`ffmpeg -v debug`), or monitoring library calls during .cine file handlingAffected if Bayer pattern images within .cine files are being decoded
-
Inspect input validation for .cine filesExamine whether any pre-processing or validation layer exists between file input and FFmpeg's libswscale that validates image height/dimensions before passing to the libraryAffected if No external validation is performed on .cine file dimensions prior to FFmpeg processing
You are affected if you run FFmpeg version 2.8.5 or earlier AND process .cine files containing Bayer format images without external height validation.
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 FFmpeg to version 2.8.6 or later which contains the fix for height validation. Alternatively, implement input validation on .cine files before passing to FFmpeg libraries, rejecting files with invalid image dimensions.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.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,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-2328 — 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-2328 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