dbcve.org
FfmpegApplication

CVE-2013-0874

HIGH · 9.3 CVSS v2.0 Published 2013-11-23
Fix available
A fix is available. Upgrade to after 1.1.2 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 (1) doubles2str and (2) shorts2str functions in libavcodec/tiff.c in FFmpeg before 1.1.3 allow remote attackers to have an unspecified impact via a crafted TIFF image, related to 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

This is an out-of-bounds array access vulnerability in FFmpeg's TIFF image decoder. The doubles2str and shorts2str functions in libavcodec/tiff.c fail to perform proper bounds checking when parsing crafted TIFF images, allowing attackers to read or write beyond allocated memory boundaries.

MitigationUpgrade to FFmpeg 1.1.3 or later which contains the bounds-checking fix. Until patched, avoid processing untrusted TIFF files with vulnerable FFmpeg versions.

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.2= 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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/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. Locate FFmpeg installation
    Run 'which ffmpeg' on Linux/macOS or check common installation paths (C:\Program Files\FFmpeg\bin\ffmpeg.exe on Windows). Also check for libavcodec shared libraries in system paths.
    Affected if FFmpeg binary or library is not found - the system is not affected.
  2. Determine FFmpeg version
    Run 'ffmpeg -version' and note the version number in the output (format: ffmpeg version X.Y.Z). For library-based installations, check libavcodec version via 'ffmpeg -version' or by inspecting the shared library file metadata.
    Affected if The version cannot be determined - further investigation needed.
  3. Compare against affected versions
    Compare the installed version to the affected list: <= 1.1.2, or exactly 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. Use 'ffmpeg -version | grep -oP "\d+\.\d+\.\d+"' to extract the version string.
    Affected if The installed version matches any of the affected versions listed above - the system is vulnerable.
  4. Check for TIFF file processing
    Review logs, scripts, or applications that use FFmpeg to process image files. Look for commands or code that decode TIFF files (ffmpeg -i input.tiff, or programmatic use of avcodec_decode_video2 with TIFF as input).
    Affected if FFmpeg processes untrusted TIFF files with a vulnerable version - exploitation is possible.

A system is affected only if it runs a vulnerable FFmpeg version (0.3.x through 0.4.6, or <=1.1.2) AND that installation is used to process TIFF image 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.2
Interim mitigation

Upgrade to FFmpeg 1.1.3 or later which contains the bounds-checking fix. Until patched, avoid processing untrusted TIFF files with vulnerable FFmpeg versions.

Recommended fix High confidence

FFmpeg 1.1.3

  1. Check current FFmpeg version using 'ffmpeg -version'
  2. Download FFmpeg 1.1.3 or later from the official source (ffmpeg.org/download.html or build from source)
  3. Install the updated FFmpeg version using your system's package manager or compile from source
  4. Verify the fix by running 'ffmpeg -version' to confirm version 1.1.3 or later is installed
  5. Test that video processing functionality still works correctly with your specific use cases
Caveat Point release upgrade (1.1.2 to 1.1.3) - primarily bug and security fixes; minimal risk but test your specific workflows

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

Fix this in Ffmpeg Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0874 — 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-0874 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