dbcve.org
FfmpegApplication

CVE-2013-0864

HIGH · 10.0 CVSS v2.0 Published 2013-11-23
Fix available
A fix is available. Upgrade to after 1.1.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The gif_copy_img_rect function in libavcodec/gifdec.c in FFmpeg before 1.1.2 performs an incorrect calculation for an "end pointer," which allows remote attackers to have an unspecified impact via crafted GIF data that triggers an out-of-bounds array access.

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 confidence

FFmpeg before 1.1.2 contains an off-by-one error in the gif_copy_img_rect function in libavcodec/gifdec.c where an incorrect calculation for an end pointer causes out-of-bounds array access when processing crafted GIF data.

MitigationUpgrade FFmpeg to version 1.1.2 or later to obtain the corrected end pointer calculation in the GIF decoder.

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
FfmpegApplication
Affected:<= 1.1.1= 0.3= 0.3.1= 0.3.2= 0.3.3= 0.3.4= 0.4.0= 0.4.2= 0.4.3= 0.4.4= 0.4.5= 0.4.6

CVSS 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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if FFmpeg is installed
    Run 'ffmpeg -version' on the command line
    Affected if The command fails or ffmpeg is not found, meaning FFmpeg is not present and this CVE does not apply
  2. Identify the installed FFmpeg version
    Run 'ffmpeg -version' and parse the version number from the output (e.g., 'ffmpeg version 0.4.6' or 'ffmpeg version 1.1.1')
    Affected if The version number is 1.1.1 or lower, or falls within the 0.3.x or 0.4.x series listed in affected versions (0.3, 0.3.1, 0.3.2, 0.3.3, 0.3.4, 0.4.0, 0.4.2, 0.4.3, 0.4.4, 0.4.5, 0.4.6)
  3. Verify GIF decoding support is enabled
    Run 'ffmpeg -formats' and search for 'gif' in the output, or run 'ffmpeg -decoders' and look for 'gif' listed under video decoders
    Affected if GIF decoder is listed as available; without GIF support enabled, the vulnerable code path cannot be triggered
  4. Confirm the vulnerable code path exists
    Inspect the file libavcodec/gifdec.c in the installed FFmpeg source or binary for the gif_copy_img_rect function and check if the end pointer calculation uses the flawed logic (compare against the patched version 1.1.2)
    Affected if The function contains the off-by-one error in end pointer calculation, meaning the code accesses memory beyond array bounds when processing crafted GIF data

You are affected if FFmpeg is installed with a version in the affected list (1.1.1 or lower, or any 0.3.x or 0.4.x version) and the GIF decoder is available and being used to process untrusted GIF files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.1.1
Interim mitigation

Upgrade FFmpeg to version 1.1.2 or later to obtain the corrected end pointer calculation in the GIF decoder.

Recommended fix High confidence

FFmpeg 1.1.2 or later; recommended: latest stable release (currently 6.x or newer)

  1. 1. Identify the current FFmpeg version by running: ffmpeg -version
  2. 2. If using a package manager (apt, yum, dnf, brew, etc.), update to the latest available version
  3. 3. For source compilation, download the latest stable release from https://ffmpeg.org/download.html or the official GitHub repository
  4. 4. Verify the upgrade was successful by running: ffmpeg -version
  5. 5. Test that your critical video processing workflows function correctly with the new version
Caveat FFmpeg has deprecated some legacy codecs and filters between 0.3.x/1.x and modern versions; test workflows thoroughly before deploying to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ffmpeg Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0864 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-0864 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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