CVE-2016-2213
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 jpeg2000_decode_tile function in libavcodec/jpeg2000dec.c in FFmpeg before 2.8.6 allows remote attackers to cause a denial of service (out-of-bounds array read access) via crafted JPEG 2000 data.
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 buffer read overflow vulnerability exists in FFmpeg's JPEG 2000 decoder. The jpeg2000_decode_tile function in libavcodec/jpeg2000dec.c lacks proper bounds checking when processing crafted JPEG 2000 data, allowing out-of-bounds array read access that leads to denial of service.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/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.
-
Check installed FFmpeg versionRun `ffmpeg -version` and examine the version number in the output (format is typically 'ffmpeg version X.Y.Z' or similar)Affected if The version displayed is 2.8.5 or lower
-
Confirm JPEG 2000 decoder availabilityRun `ffmpeg -decoders 2>/dev/null | grep -i jpeg2000` or `ffmpeg -codecs 2>/dev/null | grep -i jpeg2000` to list decodersAffected if A jpeg2000 decoder (such as jpeg2000 or libopenjpeg) appears in the output, indicating JPEG 2000 decoding capability is present
-
Verify libavcodec jpeg2000dec module existsCheck for the presence of libavcodec/jpeg2000dec.c in source installations, or check compiled binary for jpeg2000 support using `ffmpeg -hide_banner -decoders | grep -E 'jpeg2000|mj2'`Affected if JPEG 2000 or Motion JPEG 2000 decoder is compiled into or available to the FFmpeg build
-
Check if untrusted JPEG 2000 files can be processedDetermine if the FFmpeg binary has permissions and library dependencies to decode JPEG 2000 files (test with a known valid .jp2 file if available)Affected if FFmpeg can successfully decode JPEG 2000 files, meaning the vulnerable code path is reachable
A user is affected if their FFmpeg installation is version 2.8.5 or earlier and the JPEG 2000 decoder module is present and functional, allowing processing of potentially malicious JPEG 2000 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 dataUpgrade FFmpeg to version 2.8.6 or later to patch the vulnerable jpeg2000_decode_tile function. Until patched, avoid processing untrusted JPEG 2000 files with vulnerable FFmpeg instances.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-2213 — 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-2213 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