CVE-2024-1580
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 · uneditedAn integer overflow in dav1d AV1 decoder that can occur when decoding videos with large frame size. This can lead to memory corruption within the AV1 decoder. We recommend upgrading past version 1.4.0 of dav1d.
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 confidenceInteger overflow vulnerability in the dav1d AV1 video decoder that occurs when processing videos with large frame sizes. The overflow leads to incorrect memory allocation sizes, resulting in heap-based memory corruption that could allow remote code execution or denial of service.
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< 17.4.1= 40< 1.4.0< 16.7.7>= 17.0, < 17.4.1< 16.7.7>= 17.0, < 17.4.1>= 13.0, < 13.6.6>= 14.0, < 14.4.1< 1.1.1CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check dav1d library version on Linux systemsRun 'dav1d --version' or check the library file version with 'rpm -qa | grep dav1d' (Fedora) or 'dpkg -l | grep dav1d' (Debian-based)Affected if Installed version is less than 1.4.0
-
Check Safari version on macOSOpen Safari > Safari menu > About Safari, or run 'defaults read /Applications/Safari.app/Contents/Info CFBundleShortVersionString' in TerminalAffected if Safari version is below 17.4.1 on macOS 13.x-14.x
-
Check macOS version for Safari compatibilityClick Apple menu > About This Mac, or run 'sw_vers' in TerminalAffected if Running macOS 13.0-13.6.5 or 14.0-14.3 (Safari bundled with these versions is affected)
-
Check iOS/iPadOS versionGo to Settings > General > About, or check via Apple Configurator or MDMAffected if iOS or iPadOS version is 16.7.x or 17.0-17.4.0 (these versions contain affected dav1d)
-
Verify AV1 video decoding capability is accessibleAttempt to play an AV1 video file using the affected application (Safari, VLC with dav1d, or system decoder). Large frame size (4K+) AV1 files trigger the vulnerable code path.Affected if The application can decode AV1 videos and the file has frame dimensions that could trigger integer overflow (very large resolutions)
You are affected if your dav1d library is below 1.4.0, or if you run Safari on macOS < 13.6.6 / 14.4.1, or iOS/iPadOS < 16.7.7 / 17.0-17.4.1, AND you process AV1 video content with large frame sizes.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.1.11.4.013.6.6
Upgrade dav1d library to version 1.4.0 or later to remediate this vulnerability. Validate all AV1 video input processing and implement bounds checking on frame dimension calculations as defense-in-depth.
dav1d version 1.4.0 or later (or corresponding OS/browser updates: Safari 17.4.1+, macOS 13.6.6+, macOS 14.4.1+, iOS/iPadOS 16.7.7+, iOS/iPadOS 17.4.1+, visionOS 1.1.1+)
- Identify all systems or applications using the dav1d AV1 decoder library
- Check current installed version of dav1d (e.g., `dav1d --version` or via package manager)
- Update dav1d to version 1.4.0 or later using your system's package manager or by compiling from source
- For Fedora 40 users: Run `sudo dnf update dav1d` to install the patched version
- For macOS users: Ensure Safari is updated to 13.6.6 or later (for macOS 13.x) or 14.4.1 or later (for macOS 14.x)
- For iOS/iPadOS users: Update to iOS/iPadOS 16.7.7 or later, or 17.4.1 or later
- For visionOS users: Update to visionOS 1.1.1 or later
- Verify the installed version meets the minimum requirement of 1.4.0
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1580 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-1580 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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