dbcve.org
FfmpegApplication

CVE-2023-51793

HIGH · 7.8 CVSS v3.1 Published 2024-04-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Buffer Overflow vulnerability in Ffmpeg v.N113007-g8d24a28d06 allows a local attacker to execute arbitrary code via the libavutil/imgutils.c:353:9 in image_copy_plane.

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 overflow vulnerability exists in FFmpeg's image_copy_plane function (libavutil/imgutils.c:353:9). The flaw allows a local attacker to execute arbitrary code by overflowing a buffer during image plane copying operations.

MitigationUpgrade to a patched version of FFmpeg that addresses the buffer overflow in imgutils.c; until then, avoid processing untrusted media files with vulnerable FFmpeg builds.

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:= 7.0= 7.0.1= 7.0.2= 7.0.3= 7.1= 7.1.1= 7.1.2= 7.1.3= 7.2= 8.0= 8.0.1= 8.1

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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' or 'ffmpeg -buildconf' to display version information
    Affected if The version displayed is any of: 7.0, 7.0.1, 7.0.2, 7.0.3, 7.1, 7.1.1, 7.1.2, 7.1.3, 7.2, 8.0, 8.0.1, or 8.1
  2. Verify libavutil library version
    Run 'ffmpeg -version 2>&1 | grep libavutil' or check the shared library file (libavutil.so on Linux, avutil.dll on Windows) for its version metadata
    Affected if The libavutil library matches the affected FFmpeg version numbers listed above
  3. Identify if image processing features are used
    Inspect application logs or code that uses FFmpeg for image operations (such as image decoding, encoding, or format conversion using libavutil/imgutils functions)
    Affected if The environment uses FFmpeg to process image planes where image_copy_plane function in libavutil/imgutils.c would be invoked

The environment is affected if FFmpeg version is 7.0 through 8.1 (inclusive) and the system processes image data using FFmpeg's image plane copying functionality.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of FFmpeg that addresses the buffer overflow in imgutils.c; until then, avoid processing untrusted media files with vulnerable FFmpeg builds.

Recommended fix Moderate confidence

FFmpeg 7.1 or later (check official FFmpeg security advisories for the exact version containing the fix)

  1. 1. Check the official FFmpeg release notes or security advisories for CVE-2023-51793 to confirm the exact fixed version
  2. 2. Download the fixed FFmpeg version from the official ffmpeg.org website or trusted mirrors
  3. 3. Verify the checksum of the downloaded binary against the published values
  4. 4. Back up your current FFmpeg installation
  5. 5. Install the upgraded version following standard installation procedures for your platform
  6. 6. Verify the installation by running 'ffmpeg -version' and confirm the new version is active
  7. 7. Test any critical video processing workflows to ensure the upgrade does not break existing functionality
Caveat Review release notes for version 7.1+ for any compatibility changes that may affect your workflows

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

Fix this in Ffmpeg Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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