dbcve.org
FfmpegApplication

CVE-2023-6605

HIGH · 7.2 CVSS v3.1 Published 2025-01-06
Fix available
A fix is available. Upgrade to after 6.0 or later.
See remediation →
81/100
Remediation priority · High
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
A flaw was found in FFmpeg's DASH playlist support. This vulnerability allows arbitrary HTTP GET requests to be made on behalf of the machine running FFmpeg via a crafted DASH playlist containing malicious URLs.

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

A Server-Side Request Forgery (SSRF) vulnerability exists in FFmpeg's DASH playlist parser. By supplying a crafted DASH playlist containing malicious URLs, an attacker can force FFmpeg to make arbitrary HTTP GET requests to internal or external resources, potentially exposing internal services or enabling further attacks.

MitigationUpdate FFmpeg to the latest patched version. If patching is not immediately feasible, implement network segmentation to restrict FFmpeg's outbound access and validate/sanitize all DASH playlist sources 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:>= 2.0, <= 6.0

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
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

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. Confirm FFmpeg is installed
    Run 'ffmpeg -version' or 'which ffmpeg' to verify FFmpeg is present on the system
    Affected if FFmpeg is installed and the command returns a version number
  2. Check installed FFmpeg version
    Run 'ffmpeg -version' and parse the output to obtain the exact version number (e.g., 4.4.1, 5.1, 6.0)
    Affected if The installed version falls within the range >= 2.0 and <= 6.0
  3. Identify if DASH playlist processing occurs
    Search for ffmpeg commands or scripts that process .mpd files (DASH manifests), or monitor network connections initiated by ffmpeg when processing DASH streams
    Affected if FFmpeg is being used to process DASH playlists (.mpd files) from untrusted or external sources
  4. Inspect DASH playlist sources
    Review logs, configurations, or scripts that reference DASH streams; examine the origin of .mpd files being processed (local files vs. remote URLs)
    Affected if DASH playlists are loaded from external or untrusted URLs that could contain malicious URL payloads
  5. Review network activity during DASH processing
    Use network monitoring (e.g., tcpdump, Wireshark) or proxy logs to observe HTTP requests made by ffmpeg during DASH segment retrieval
    Affected if ffmpeg makes HTTP requests to unexpected or internal IP addresses when processing DASH content

You are affected if FFmpeg version 2.0 through 6.0 is installed and the system processes DASH playlists from external or untrusted sources.

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 6.0
Interim mitigation

Update FFmpeg to the latest patched version. If patching is not immediately feasible, implement network segmentation to restrict FFmpeg's outbound access and validate/sanitize all DASH playlist sources before processing.

Recommended fix Moderate confidence

FFmpeg 6.1 or later

  1. 1. Identify the current FFmpeg version by running 'ffmpeg -version'
  2. 2. Download or obtain FFmpeg 6.1 or later from the official source (https://ffmpeg.org/download.html) or your system's package manager
  3. 3. Backup any existing FFmpeg installation and custom configurations
  4. 4. Install the updated FFmpeg version using your system's package manager or compile from source
  5. 5. Verify the installation was successful by running 'ffmpeg -version' and confirming the new version number
  6. 6. Test that DASH playlist functionality works correctly with your intended use cases
Caveat Major version upgrades in FFmpeg can include API changes, removed codecs, or altered default behaviors; review the FFmpeg 6.1 release notes for any breaking changes relevant to your workflows

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

Fix this in Ffmpeg Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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