dbcve.org
macOSOperating system · Apple

CVE-2024-40774

HIGH · 7.1 CVSS v3.1 Published 2024-07-29
Fix available
A fix is available. Upgrade to 10.6 / 12.7.6 or later.
See remediation →
73/100
Remediation priority · Elevated
Zero-click

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 · unedited
A downgrade issue was addressed with additional code-signing restrictions. This issue is fixed in iOS 17.6 and iPadOS 17.6, macOS Monterey 12.7.6, macOS Sonoma 14.6, macOS Ventura 13.6.8, tvOS 17.6, watchOS 10.6. 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 · high confidence

A code-signing bypass vulnerability in Apple operating systems allowed malicious apps to perform a downgrade attack, bypassing Privacy preferences through flaws in code-signing validation. This could enable unauthorized access to sensitive user data or system features that should require explicit user consent.

MitigationApply the available security updates (iOS 17.6, iPadOS 17.6, macOS Monterey 12.7.6, macOS Sonoma 14.6, macOS Ventura 13.6.8, tvOS 17.6, watchOS 10.6) to all affected devices to restore proper code-signing restrictions.

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
macOSOperating system
Affected:< 12.7.6>= 13.0, < 13.6.8>= 14.0, < 14.6
Iphone OsOperating system
Affected:< 17.6
IpadosOperating system
Affected:< 17.6
WatchosOperating system
Affected:< 10.6
TvosOperating system
Affected:< 17.6

CVSS 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
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check macOS version
    Run 'sw_vers -productVersion' in Terminal or open System Settings > About > Version
    Affected if Version is below 12.7.6, or between 13.0 and 13.6.7, or between 14.0 and 14.5
  2. Check iOS version
    Open Settings > General > About > Version on the iPhone
    Affected if Version is below 17.6
  3. Check iPadOS version
    Open Settings > General > About > Version on the iPad
    Affected if Version is below 17.6
  4. Check watchOS version
    Open the Watch app on iPhone > My Watch > General > About > Version, or on the watch go to Settings > General > About
    Affected if Version is below 10.6
  5. Check tvOS version
    Open Settings > General > About > Version on Apple TV
    Affected if Version is below 17.6

If the installed OS version falls within any of the vulnerable ranges (below 12.7.6 for Monterey, 13.0-13.6.7 for Ventura, 14.0-14.5 for Sonoma, or below 17.6 for iOS/iPadOS/tvOS/watchOS), the code-signing bypass vulnerability is present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.6 / 12.7.6 / 13.6.8 or later
Fixed in 10.612.7.613.6.8
Interim mitigation

Apply the available security updates (iOS 17.6, iPadOS 17.6, macOS Monterey 12.7.6, macOS Sonoma 14.6, macOS Ventura 13.6.8, tvOS 17.6, watchOS 10.6) to all affected devices to restore proper code-signing restrictions.

Recommended fix High confidence

iOS 17.6 / iPadOS 17.6 / macOS Monterey 12.7.6 / macOS Ventura 13.6.8 / macOS Sonoma 14.6 / watchOS 10.6 / tvOS 17.6

  1. For iOS/iPadOS: Go to Settings > General > Software Update and install iOS 17.6/iPadOS 17.6
  2. For macOS Monterey (12.x): Go to System Settings > General > Software Update and install version 12.7.6
  3. For macOS Ventura (13.x): Go to System Settings > General > Software Update and install version 13.6.8
  4. For macOS Sonoma (14.x): Go to System Settings > General > Software Update and install version 14.6
  5. For watchOS: Go to Settings > General > Software Update on the paired iPhone or directly on Apple Watch and install watchOS 10.6
  6. For tvOS: Go to Settings > General > Software Update and install tvOS 17.6
  7. After updating, verify the installed version matches the fixed release
Caveat Security-only updates typically have no functional breaking changes; however, always test critical workflows after updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in macOS Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-40774 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-40774 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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