dbcve.org
FfmpegApplication

CVE-2013-0844

HIGH · 9.3 CVSS v2.0 Published 2013-12-07
Fix available
A fix is available. Upgrade to after 1.0.3 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
Off-by-one error in the adpcm_decode_frame function in libavcodec/adpcm.c in FFmpeg before 1.0.4 allows remote attackers to have an unspecified impact via crafted DK4 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

Off-by-one error in the adpcm_decode_frame function in libavcodec/adpcm.c in FFmpeg versions before 1.0.4 allows out-of-bounds array access when processing crafted DK4 ADPCM audio data, potentially enabling remote code execution.

MitigationUpgrade FFmpeg to version 1.0.4 or later in all affected deployments and ensure media processing pipelines use the patched library version.

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.0.3= 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. Find FFmpeg installation
    Run 'ffmpeg -version' or 'ffprobe -version' to check if FFmpeg tools are installed. Also check for libavcodec library files (libavcodec.so* on Linux, avcodec.dll on Windows) in system paths.
    Affected if FFmpeg or libavcodec is present on the system
  2. Identify the exact version
    Parse the version string from the output of 'ffmpeg -version' or examine the library file metadata. For static builds, check any version indicator in the binary or accompanying files.
    Affected if The version is 1.0.3 or earlier, or matches 0.3.x (0.3, 0.3.1, 0.3.2, 0.3.3, 0.3.4) or 0.4.x (0.4.0, 0.4.2, 0.4.3, 0.4.4, 0.4.5, 0.4.6)
  3. Verify ADPCM decoder is available
    Run 'ffmpeg -codecs 2>/dev/null | grep -i adpcm' or 'ffprobe -codecs 2>/dev/null | grep -i adpcm' to list available ADPCM decoders.
    Affected if ADPCM decoders (including DK4) are listed as supported codecs
  4. Confirm the vulnerable code path can be triggered
    Review media processing workflows or applications that use this FFmpeg library to determine if they process DK4 ADPCM audio files. Check for any audio files with .dk4 extension or content identified as 'DK4' ADPCM format.
    Affected if The environment processes or can process DK4 ADPCM audio data using the affected FFmpeg version

The environment is affected if FFmpeg or libavcodec with a version in the affected list (1.0.3 or earlier, or specific 0.3.x/0.4.x versions) is installed and the ADPCM decoder is available for processing DK4 audio 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.0.3
Interim mitigation

Upgrade FFmpeg to version 1.0.4 or later in all affected deployments and ensure media processing pipelines use the patched library version.

Recommended fix High confidence

FFmpeg 1.0.4 or later

  1. 1. Identify the current FFmpeg version installed using: ffmpeg -version
  2. 2. Download FFmpeg version 1.0.4 or later from the official source (ffmpeg.org/download.html)
  3. 3. Stop any services or applications using FFmpeg
  4. 4. Uninstall the current FFmpeg version
  5. 5. Install the new FFmpeg version (1.0.4 or later)
  6. 6. Verify the installation by running: ffmpeg -version
  7. 7. Restart any affected services
Caveat Minor: Ensure any custom build scripts or integration points reference the correct version path; the adpcm decoder API remains compatible

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
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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