Ubuntu LinuxOperating system · Canonical
CVE-2015-8364
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 ff_ivi_init_planes function in libavcodec/ivi.c in FFmpeg before 2.6.5, 2.7.x before 2.7.3, and 2.8.x through 2.8.2 allows remote attackers to cause a denial of service (out-of-bounds heap-memory access) or possibly have unspecified other impact via crafted image dimensions in Indeo Video Interactive 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 confidenceInteger overflow in the ff_ivi_init_planes function in libavcodec/ivi.c when processing crafted image dimensions in Indeo Video Interactive data. The overflow allows attackers to trigger out-of-bounds heap-memory access via maliciously crafted video files, potentially leading to denial of service or 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
Ubuntu LinuxOperating system
= 12.04= 2.6.4= 2.7.0= 2.7.1= 2.7.2= 2.8.0= 2.8.1= 2.8.2CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 package manager (e.g., `dpkg -l | grep ffmpeg` on Debian/Ubuntu, `rpm -qa | grep ffmpeg` on RHEL/CentOS)Affected if The version matches 2.6.4, 2.7.0, 2.7.1, 2.7.2, 2.8.0, 2.8.1, or 2.8.2
-
Check if libavcodec is presentRun `ffmpeg -codecs 2>/dev/null | grep -i ivi` or look for the shared library file (e.g., `ls /usr/lib/*/libavcodec.so*` on Linux)Affected if The Indeo Video decoder (ivi) is available in the FFmpeg installation
-
Verify the vulnerable code path is reachableConfirm that your FFmpeg build includes the Indeo Video Interactive decoder; run `ffmpeg -decoders 2>/dev/null | grep -i indeo`Affected if The decoder is present and enabled, allowing processing of .ivi or related Indeo video files
-
Confirm application usage of the affected componentAudit any custom code or scripts that invoke ffmpeg or link against libavcodec to process video files, especially those that may handle Indeo format inputAffected if Your environment uses FFmpeg or libavcodec to process untrusted Indeo video files
You are affected if FFmpeg version 2.6.4, 2.7.x up to 2.7.2, or 2.8.x up to 2.8.2 is installed AND the Indeo Video decoder (ivi) is available and used to process video 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 to FFmpeg 2.6.5, 2.7.3, or 2.8.3 and later versions. Alternatively, implement input validation on image dimensions in the Indeo Video decoder to reject values that could cause integer overflow before memory allocation.
Fix this in Ubuntu Linux
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-8364 — 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-2015-8364 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