CVE-2024-40775
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 Monterey 12.7.6, macOS Sonoma 14.6, macOS Ventura 13.6.8. An app may be able to leak sensitive user information.
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 macOS code-signing downgrade vulnerability that allowed an application to bypass security restrictions and leak sensitive user information. The issue involved exploiting the code-signing mechanism to revert to less secure states, potentially exposing private data.
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< 12.7.6>= 13.0, < 13.6.8>= 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 versionRun `sw_vers` in Terminal or go to Apple menu > About This MacAffected if Version is earlier than 12.7.6, or between 13.0-13.6.7, or between 14.0-14.5 (vulnerable to code-signing downgrade)
-
Confirm macOS build numberRun `uname -a` in Terminal to see kernel and build detailsAffected if Build date predates the security update release for your macOS version
-
Check if code-signed applications are in useUse `codesign -dv /path/to/application.app 2>&1` to inspect code-signing status of any applicationAffected if Applications with code signatures are present (the vulnerability affects code-signing enforcement for any signed app)
You are affected if your macOS version is below 12.7.6, between 13.0-13.6.7, or between 14.0-14.5, as these versions contain the vulnerable code-signing mechanism.
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 · scoped12.7.613.6.814.6
Apply the macOS security updates (Monterey 12.7.6, Ventura 13.6.8, or Sonoma 14.6 depending on your macOS version) to address the code-signing downgrade vulnerability.
macOS Monterey 12.7.6, macOS Ventura 13.6.8, or macOS Sonoma 14.6 (depending on your current macOS version)
- Open System Settings (or System Preferences on older macOS versions)
- Navigate to General > Software Update
- Click "Check for Update" or allow the system to automatically check
- If an update is available, click "Download and Install"
- Wait for the download to complete and follow any prompts to restart
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-40775 — 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-40775 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