dbcve.org
FfmpegApplication

CVE-2019-13312

HIGH · 8.8 CVSS v3.0 Published 2019-07-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
block_cmp() in libavcodec/zmbvenc.c in FFmpeg 4.1.3 has a heap-based buffer over-read.

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

Heap-based buffer over-read vulnerability in FFmpeg 4.1.3's zmbv (Zip Motion Blocks Video) encoder. The block_cmp() function in libavcodec/zmbvenc.c reads beyond allocated buffer boundaries, potentially allowing disclosure of heap memory contents or denial of service when processing maliciously crafted video files.

MitigationUpdate to a patched version of FFmpeg that addresses CVE-2019-13312. If updating is not immediately feasible, disable or restrict zmbv codec usage in media processing pipelines and validate input before processing.

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:= 4.1.3

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
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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' and examine the version string. Look specifically for version 4.1.3.
    Affected if The output shows version 4.1.3 exactly.
  2. Verify zmbv codec availability
    Run 'ffmpeg -codecs | grep zmbv' to list encoders and decoders. Look for zmbv entries showing encoding (E) and decoding (D) capabilities.
    Affected if The zmbv encoder (zmbv) appears in the codec list with encoding capability.
  3. Identify active zmbv encoding processes
    Run 'ps aux | grep -i ffmpeg' or check running processes for any that invoke the zmbv encoder (via -c:v zmbv or similar).
    Affected if Any running FFmpeg process is actively encoding video using the zmbv codec.
  4. Inspect recent media files for zmbv usage
    Examine recently created video files using 'ffprobe -show_streams <file>' and look for codec_name: zmbv in the video stream.
    Affected if Any recently processed video files show zmbv as the video codec.

You are affected if FFmpeg version 4.1.3 is installed AND the zmbv encoder is being used to process video 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of FFmpeg that addresses CVE-2019-13312. If updating is not immediately feasible, disable or restrict zmbv codec usage in media processing pipelines and validate input before processing.

Fix this in Ffmpeg Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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