CVE-2024-40814
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 · uneditedA downgrade issue was addressed with additional code-signing restrictions. This issue is fixed in macOS Sonoma 14.6, macOS Ventura 13.7. An app may be able to bypass Privacy preferences.
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 confidenceThis is a code-signing bypass vulnerability in macOS where an application could potentially bypass Privacy preferences (likely TCC - Transparency, Consent, and Control protections) through a downgrade attack. The issue was addressed by implementing additional code-signing restrictions in macOS Sonoma 14.6 and Ventura 13.7.
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.0, < 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 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 -productVersion` in TerminalAffected if Version is 14.0, 14.1, 14.2, 14.3, 14.4, or 14.5 (any build between 14.0 and <14.6)
-
Confirm macOS release nameThe affected range applies to macOS Sonoma (version 14.x). If running macOS Ventura (13.x) or earlier, this specific CVE does not apply to that major versionAffected if Running macOS Sonoma 14.0 through 14.5
-
Verify system is not patchedCheck that the installed build matches a pre-patch version. The patch was released in macOS Sonoma 14.6. Run `uname -a` to see kernel version if neededAffected if System has not been updated to macOS Sonoma 14.6 or later
You are affected if your Mac is running macOS Sonoma version 14.0 through 14.5; update to 14.6 or later to resolve.
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-supplied macOS security updates (Sonoma 14.6 or Ventura 13.7) to patch the code-signing bypass. No further configuration is required beyond standard OS patching.
macOS Sonoma 14.6 or later (or macOS Ventura 13.7 if staying on Ventura)
- Back up your Mac using Time Machine or another backup solution before updating
- Open System Settings (or System Preferences on older macOS versions)
- Navigate to General > Software Update
- Allow the system to check for updates
- If macOS 14.6 (Sonoma) is available, click "Update Now" to install it
- Restart your Mac when prompted to complete the installation
- After updating, verify the update by checking System Settings > General > About > macOS version (should show 14.6 or later)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-40814 — 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-40814 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