CVE-2014-9318
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 raw_decode function in libavcodec/rawdec.c in FFMpeg before 2.1.6, 2.2.x through 2.3.x, and 2.4.x before 2.4.4 allows remote attackers to cause a denial of service (out-of-bounds heap access) and possibly have other unspecified impact via a crafted .cine file that triggers the avpicture_get_size function to return a negative frame size.
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 confidenceThe raw_decode function in FFmpeg's libavcodec/rawdec.c fails to properly validate the return value from avpicture_get_size when processing .cine files. When a crafted .cine file triggers avpicture_get_size to return a negative value, this negative size is used in heap operations, causing out-of-bounds memory access and potential 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.1.5= 2.2= 2.2.4= 2.3= 2.3.2= 2.3.3= 2.3.4= 2.3.5= 2.4= 2.4.1= 2.4.2= 2.4.3CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/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.
-
Check if FFmpeg is installedRun `ffmpeg -version` or `which ffmpeg` to confirm the binary existsAffected if FFmpeg is not installed or not in PATH
-
Identify the installed FFmpeg versionRun `ffmpeg -version` and parse the version number from the output (e.g., 'ffmpeg version 2.4.2')Affected if The version falls within the affected range: <= 2.1.5, 2.2.x, 2.3.x (any), 2.4.x through 2.4.3
-
Verify .cine demuxer support is availableRun `ffmpeg -formats 2>/dev/null | grep -i cine` or `ffmpeg -codecs 2>/dev/null | grep -i cine` to check if the cine format is recognizedAffected if The .cine demuxer is listed as supported, indicating the vulnerable code path could be reached
-
Confirm libavcodec version matches vulnerable releaseRun `ffmpeg -version 2>&1 | grep 'libavcodec'` to check the linked libavcodec versionAffected if The libavcodec version matches the vulnerable FFmpeg version numbers listed above
A user is affected if they have a vulnerable FFmpeg version (2.1.5 or earlier, or 2.2 through 2.4.3) AND have the .cine demuxer/codec support enabled, allowing them to process potentially crafted .cine 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.4.4, 2.1.6, or later. Alternatively, disable processing of untrusted .cine files until the upgrade is applied.
- 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-2014-9318 — 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-2014-9318 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