CVE-2014-5272
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 · uneditedlibavcodec/iff.c in FFMpeg before 1.1.14, 1.2.x before 1.2.8, 2.2.x before 2.2.7, and 2.3.x before 2.3.2 allows remote attackers to have unspecified impact via a crafted iff image, which triggers an out-of-bounds array access, related to the rgb8 and rgbn formats.
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 · moderate confidenceOut-of-bounds array access vulnerability in libavcodec/iff.c when processing crafted IFF image files. The vulnerability specifically affects rgb8 and rgbn format handling, allowing unspecified impact via malformed image input.
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<= 1.1.13= 1.1= 1.1.1= 1.1.2= 1.1.3= 1.1.4= 1.1.5= 1.1.6= 1.1.7= 1.1.8= 1.1.9= 1.1.10CVSS 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.
-
Check installed FFmpeg versionRun `ffmpeg -version` or `ffmpeg 2>&1 | head -1` to retrieve the version stringAffected if The version is 1.1.x where x is 0-13, or any version <= 1.1.13 (1.1, 1.1.1, 1.1.2, etc.)
-
Verify libavcodec versionRun `ffmpeg -version` and look for the libavcodec version in the output (typically shown as 'libavcodec version XX' or part of the ffmpeg version string)Affected if The libavcodec version corresponds to FFmpeg 1.1.x through 1.1.13 inclusive
-
Confirm IFF decoder availabilityRun `ffmpeg -decoders 2>&1 | grep -i iff` or `ffmpeg -formats 2>&1 | grep -i iff` to list IFF-related decoders and formatsAffected if IFF decoder is present and IFF image files can be processed by the installation
-
Check for rgb8 and rgbn format support in IFFRun `ffmpeg -pix_fmts 2>&1` or inspect decoder output for supported pixel formats; look for 'rgb8' or 'rgbn' in the context of IFF processingAffected if The build includes support for rgb8 or rgbn pixel formats in the IFF decoder, enabling the vulnerable code path
You are affected if your FFmpeg version is 1.1.x up to 1.1.13 inclusive and you process IFF image files (particularly rgb8 or rgbn formats) with the installed libavcodec.
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 1.1.14, 1.2.8, 2.2.7, 2.3.2 or later. If upgrading is not immediately feasible, implement input validation for IFF images before passing to libavcodec.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-5272 — 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-5272 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