CVE-2024-40845
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 · uneditedThe issue was addressed with improved memory handling. This issue is fixed in macOS Sequoia 15, macOS Sonoma 14.7. Processing a maliciously crafted video file may lead to unexpected app termination.
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 confidenceA memory handling vulnerability exists in macOS video processing components. Processing a maliciously crafted video file triggers improper memory operations, causing unexpected application termination due to memory corruption.
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< 14.7CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed macOS versionGo to Apple menu > About This Mac, or run 'sw_vers' in Terminal, or check /System/Library/CoreServices/SystemVersion.plistAffected if Version is below 14.7 (Sonoma)
-
Identify video processing applications in useReview installed applications for video editors, players, or converters (e.g., QuickTime, Final Cut, VLC, third-party video tools). Check /Applications folder for video-related software.Affected if Any video processing application is installed and used
-
Check for recent video file processing activityExamine system logs for crashes or termination events related to video components: grep -i 'video' /var/log/system.log (or use Console app to search for CoreMedia, AVFoundation, or video-related crash reports)Affected if Logs show unexpected application termination during video file processing
-
Verify video file handling is enabledConfirm that the system can process video files by checking if video codecs or handlers are registered: ls /System/Library/QuickTime/ or check Video Toolbox framework presenceAffected if Video processing frameworks are present and functional
User is affected if running macOS version below 14.7 AND actively processes video files using native or third-party video handling components.
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 · scoped14.7
Apply the vendor-supplied patches by updating macOS to version 15 (Sequoia) or 14.7 (Sonoma), which contain corrected memory handling routines for video file processing.
macOS Sonoma 14.7 or macOS Sequoia 15
- Upgrade macOS Sonoma to version 14.7 or later via System Settings > General > Software Update
- Alternatively, upgrade to macOS Sequoia 15 via System Settings > General > Software Update
- After upgrading, ensure the VideoProc application or any video processing software is updated to the latest version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-40845 — 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-40845 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