dbcve.org
FfmpegApplication

CVE-2013-0875

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 ff_add_png_paeth_prediction function in libavcodec/pngdec.c in FFmpeg before 1.1.3 allows remote attackers to have an unspecified impact via a crafted PNG 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 · moderate confidence

This is an out-of-bounds array access vulnerability in FFmpeg's PNG decoder (libavcodec/pngdec.c) in the ff_add_png_paeth_prediction function, affecting versions prior to 1.1.3. Attackers can trigger the vulnerability by serving a specially crafted PNG image, potentially allowing remote code execution or denial of service.

MitigationUpgrade FFmpeg to version 1.1.3 or later to obtain the patched code, or apply the vendor-provided security patch to the ff_add_png_paeth_prediction function.

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. Identify FFmpeg version
    Run 'ffmpeg -version' or 'avconv -version' to display the installed version number
    Affected if The version is 1.1.2 or earlier, or matches 0.3.x through 0.4.6 as listed in affected versions
  2. Locate the vulnerable library
    Check for the presence of libavcodec/pngdec.c or the compiled libavcodec library (libavcodec.so or .dll) in the system
    Affected if The library exists and the version is in the affected range
  3. Confirm PNG decoding usage
    Inspect running processes or logs for PNG file decoding operations using ffmpeg/avconv commands, or check if applications link against libavcodec for PNG handling
    Affected if PNG images are being decoded by the affected FFmpeg library version
  4. Verify vulnerable function presence
    If source code is available, search for the ff_add_png_paeth_prediction function in libavcodec/pngdec.c and check if it contains the out-of-bounds array access pattern
    Affected if The function exists without the bounds-checking fix and the library version is affected

A user is affected if their installed FFmpeg version is 1.1.2 or earlier (including 0.3.x through 0.4.6) and they decode PNG images using the vulnerable library.

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 FFmpeg to version 1.1.3 or later to obtain the patched code, or apply the vendor-provided security patch to the ff_add_png_paeth_prediction function.

Recommended fix High confidence

FFmpeg 1.1.3 or later (preferably latest stable release)

  1. 1. Check the current installed FFmpeg version using: ffmpeg -version
  2. 2. Backup any custom FFmpeg configuration or scripts that may depend on specific FFmpeg versions
  3. 3. Remove the existing FFmpeg installation (on Debian/Ubuntu: sudo apt-get remove ffmpeg; on RHEL/CentOS: sudo yum remove ffmpeg)
  4. 4. Install FFmpeg 1.1.3 or later from source or official repositories: git clone git://source.ffmpeg.org/ffmpeg.git && cd ffmpeg && git checkout release/1.1.3
  5. 5. Configure and compile: ./configure && make && sudo make install
  6. 6. Verify the new version: ffmpeg -version
  7. 7. Test with the previously vulnerable PNG files to confirm the fix is applied
Caveat Minor version bump; likely minimal API changes between 1.1.2 and 1.1.3, but test custom integrations

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

Fix this in Ffmpeg Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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