dbcve.org
FfmpegApplication

CVE-2013-0876

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
Multiple integer overflows in the (1) old_codec37 and (2) old_codec47 functions in libavcodec/sanm.c in FFmpeg before 1.1.3 allow remote attackers to have an unspecified impact via crafted LucasArts Smush data, which 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

Multiple integer overflows in the old_codec37 and old_codec47 functions in libavcodec/sanm.c in FFmpeg allow remote attackers to cause out-of-bounds array access via crafted LucasArts Smush media files, leading to potential code execution.

MitigationUpgrade to FFmpeg 1.1.3 or later to obtain the patch that adds proper bounds checking to prevent integer overflows in the Smush format parser.

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. Check installed FFmpeg version
    Run `ffmpeg -version` to obtain the version number of the FFmpeg binary or library
    Affected if The version is 0.3 through 0.4.6, or any version 1.1.2 or earlier (including 1.1.x versions before 1.1.3)
  2. Verify Smush (sanm) decoder is available
    Run `ffmpeg -codecs 2>/dev/null | grep -i sanm` or check if libavcodec was compiled with sanm.c support
    Affected if The sanm decoder is present and enabled in the FFmpeg build
  3. Confirm Smush file processing capability
    Run `ffmpeg -formats 2>/dev/null | grep -i smush` to check if the Smush/ANM demuxer is available
    Affected if FFmpeg can demux LucasArts Smush format files
  4. Identify active Smush file processing
    Inspect any recent FFmpeg transcoding logs, scripts, or applications that process .anim, .anm, or LucasArts game media files
    Affected if FFmpeg is being used to process LucasArts Smush media files (the attack vector requires processing crafted files)

A user is affected if they run a vulnerable FFmpeg version (1.1.2 or earlier, or 0.3 through 0.4.6) AND have the Smush/sanm decoder enabled AND process untrusted LucasArts Smush media 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 to obtain the patch that adds proper bounds checking to prevent integer overflows in the Smush format parser.

Recommended fix High confidence

FFmpeg 1.1.3 or later

  1. 1. Identify the current FFmpeg version by running 'ffmpeg -version' or checking the installed package
  2. 2. Back up any custom FFmpeg configuration files or scripts that may exist
  3. 3. Remove the existing FFmpeg installation: On Debian/Ubuntu run 'sudo apt-get remove ffmpeg', on RedHat/CentOS run 'sudo yum remove ffmpeg', or on macOS with Homebrew run 'brew uninstall ffmpeg'
  4. 4. Download FFmpeg version 1.1.3 or later from the official source (ffmpeg.org/download.html) or install via package manager after updating repositories
  5. 5. Compile and install FFmpeg 1.1.3 or later: ./configure && make && sudo make install (if building from source)
  6. 6. Verify the new version is installed correctly by running 'ffmpeg -version' and confirming it shows version 1.1.3 or higher
  7. 7. Test that any critical video processing workflows still function as expected with the new version

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
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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