dbcve.org
FfmpegApplication

CVE-2018-6912

MEDIUM · 6.5 CVSS v3.0 Published 2018-02-12
Fix available
A fix is available. Upgrade to after 3.4.2 or later.
See remediation →
72/100
Remediation priority · Elevated
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
The decode_plane function in libavcodec/utvideodec.c in FFmpeg through 3.4.2 allows remote attackers to cause a denial of service (out of array read) via a crafted AVI file.

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

A buffer over-read vulnerability exists in FFmpeg's Ut Video decoder (decode_plane function in libavcodec/utvideodec.c) where processing a specially crafted AVI file causes an out-of-bounds array read, resulting in denial of service.

MitigationUpgrade FFmpeg to a version beyond 3.4.2 that contains the fix; avoid processing untrusted AVI files until patched.

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

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
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 FFmpeg version
    Run 'ffmpeg -version' and examine the output for the version number (e.g., 3.4.2, 3.4.1, etc.)
    Affected if The installed version is 3.4.2 or lower
  2. Verify Ut Video decoder presence
    Run 'ffmpeg -codecs 2>/dev/null | grep -i utvideo' or 'ffmpeg -decoders 2>/dev/null | grep -i utvideo' to confirm the Ut Video decoder is compiled into the FFmpeg build
    Affected if The Ut Video decoder (utvideo) is listed as available
  3. Confirm vulnerable code path exists
    Check if the file libavcodec/utvideodec.c exists in the FFmpeg source or installed library files, as this contains the vulnerable decode_plane function
    Affected if The utvideodec.c file is present in the installation
  4. Identify if processing untrusted AVI files
    Review logs or audit any recent AVI file processing to identify if Ut Video encoded files have been handled
    Affected if Ut Video encoded AVI files have been processed with this FFmpeg version

You are affected if FFmpeg version 3.4.2 or lower is installed AND the Ut Video decoder is available in the build AND you have processed Ut Video encoded AVI files with the vulnerable decoder.

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
Upgrade available Upgrade to a release after 3.4.2
Interim mitigation

Upgrade FFmpeg to a version beyond 3.4.2 that contains the fix; avoid processing untrusted AVI files until patched.

Fix this in Ffmpeg Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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