CVE-2024-40810
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 out-of-bounds write issue was addressed with improved input validation. This issue is fixed in macOS Sonoma 14.6. An app may be able to cause a coprocessor crash.
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 confidenceAn out-of-bounds write vulnerability in macOS Sonoma allows a malicious application to write data beyond allocated memory boundaries through improper input handling. The vulnerability affects the coprocessor subsystem and can be triggered to cause a coprocessor crash. Apple addressed this with improved input validation in macOS Sonoma 14.6.
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.6CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 versionOpen Terminal and run 'sw_vers -productVersion' or go to Apple menu > About This Mac > System Report > Software > System VersionAffected if The version returned is less than 14.6 (e.g., 14.5, 14.4, 14.3, etc.)
-
Verify macOS build numberRun 'uname -a' in Terminal or check System Information > Software > System Version for the build number (e.g., 23F79, 23F80)Affected if The build number corresponds to a macOS Sonoma version prior to the 14.6 security update release
-
Confirm macOS Sonoma is in useCheck that the system is running macOS Sonoma (14.x) rather than an older macOS version like Ventura (13.x) or earlierAffected if The system shows a major version of 14 but is below 14.6
A system is affected if it is running any version of macOS Sonoma prior to 14.6, as the vulnerability was addressed in the 14.6 security update.
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.6
Apply the vendor patch by updating affected macOS systems to version Sonoma 14.6 or later to remediate the out-of-bounds write vulnerability.
macOS Sonoma 14.6
- Back up your Mac using Time Machine or another backup method before updating
- Open System Settings (or System Preferences on older macOS versions)
- Click on General in the sidebar
- Click on Software Update
- Allow macOS to check for updates
- If macOS Sonoma 14.6 is available, click Update Now or Download and Install
- Follow the on-screen instructions to complete the installation
- Restart your Mac when prompted to complete the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-40810 — 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-40810 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