dbcve.org
Reachable AssertionWeakness · CWE-617

CVE-2025-22919

MEDIUM · 6.5 CVSS v3.1 Published 2025-02-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A reachable assertion in FFmpeg git-master commit N-113007-g8d24a28d06 allows attackers to cause a Denial of Service (DoS) via opening a crafted AAC 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 · moderate confidence

A reachable assertion in FFmpeg's AAC decoder (git-master commit N-113007-g8d24a28d06) can be triggered by a specially crafted AAC file, causing a denial of service. The assertion fails when the malformed input triggers an unexpected condition in the decoder logic.

MitigationUpdate FFmpeg to a version after commit N-113007-g8d24a28d06, or apply the specific patch that modifies the assertion behavior to proper error handling in the AAC decoder. Until patched, avoid processing untrusted AAC files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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.1/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 if FFmpeg is installed
    Run `ffmpeg -version` or `which ffmpeg`
    Affected if FFmpeg is not installed or not accessible in PATH - not affected
  2. Identify the FFmpeg version or commit
    Run `ffmpeg -version` to see the version string, or use `ffmpeg -buildinfo` to see build details including git commit info if available
    Affected if The version shows a commit hash or date that is at or before commit N-113007-g8d24a28d06 (or the version predates the fix)
  3. Confirm the AAC decoder is in use
    Inspect process logs, network captures, or application configuration to see if AAC audio decoding is being performed using FFmpeg
    Affected if The system processes untrusted AAC files through FFmpeg's native AAC decoder (libavcodec/aacdec.c) - vulnerable only when this decoder path is exercised

You are affected if FFmpeg is installed with a version at or before commit N-113007-g8d24a28d06 AND the AAC decoder is used to process potentially untrusted AAC 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 FFmpeg to a version after commit N-113007-g8d24a28d06, or apply the specific patch that modifies the assertion behavior to proper error handling in the AAC decoder. Until patched, avoid processing untrusted AAC files.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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