dbcve.org
IpadosOperating system · Apple

CVE-2024-40805

HIGH · 7.1 CVSS v3.1 Published 2024-07-29
Fix available
A fix is available. Upgrade to 10.6 / 14.6 or later.
See remediation →
74/100
Remediation priority · Elevated
No privileges

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 permissions issue was addressed with additional restrictions. This issue is fixed in iOS 17.6 and iPadOS 17.6, macOS Sonoma 14.6, 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 · moderate confidence

An app could bypass Privacy preferences on affected Apple devices (iOS 17.6 and earlier, iPadOS 17.6 and earlier, macOS Sonoma 14.6 and earlier, tvOS 17.6 and earlier, watchOS 10.6 and earlier) due to insufficient permission restrictions that were addressed with additional access controls.

MitigationUpdate all affected Apple devices to iOS 17.6/iPadOS 17.6, macOS Sonoma 14.6, tvOS 17.6, or watchOS 10.6 or later to receive the fix.

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
IpadosOperating system
Affected:< 17.6
Iphone OsOperating system
Affected:< 17.6
macOSOperating system
Affected:>= 14.0, < 14.6
TvosOperating system
Affected:< 17.6
WatchosOperating system
Affected:< 10.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
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 checks

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

  1. Identify your Apple device type
    Determine whether the device is an iPhone, iPad, Mac, Apple TV, or Apple Watch. On iPhone/iPad: Settings > General > About. On Mac: System Settings > General > About. On Apple TV: Settings > General > About. On Apple Watch: Settings > General > About.
    Affected if Device type is iPhone, iPad, Mac, Apple TV, or Apple Watch
  2. Check iOS version on iPhone or iPad
    Go to Settings > General > About and note the version number shown next to 'Software Version'.
    Affected if Version is less than 17.6 (for example, 17.5, 17.4, etc.)
  3. Check macOS version on Mac
    Go to System Settings > General > About and note the version number shown next to 'macOS'. Look for a version such as 14.5, 14.4, 14.3, 14.2, 14.1, or 14.0.
    Affected if Version is 14.0 through 14.5 (any version >= 14.0 but < 14.6)
  4. Check tvOS version on Apple TV
    Go to Settings > General > About and note the version number shown next to 'tvOS Version'.
    Affected if Version is less than 17.6
  5. Check watchOS version on Apple Watch
    On Apple Watch, go to Settings > General > About and note the version number. Alternatively, open the Watch app on paired iPhone and go to My Watch > General > About.
    Affected if Version is less than 10.6

You are affected if your device runs iOS, iPadOS, tvOS, or watchOS version less than 17.6, or macOS Sonoma version 14.0 through 14.5.

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 / 14.6 / 17.6 or later
Fixed in 10.614.617.6
Interim mitigation

Update all affected Apple devices to iOS 17.6/iPadOS 17.6, macOS Sonoma 14.6, tvOS 17.6, or watchOS 10.6 or later to receive the fix.

Recommended fix High confidence

iOS 17.6, iPadOS 17.6, macOS Sonoma 14.6, tvOS 17.6, watchOS 10.6

  1. Back up your device data before updating to ensure no data loss occurs
  2. For iPhone and iPad: Go to Settings > General > Software Update and install iOS 17.6 or iPadOS 17.6
  3. For Mac: Open System Settings > General > Software Update and install macOS Sonoma 14.6
  4. For Apple TV: Go to Settings > System > Software Updates and install tvOS 17.6
  5. For Apple Watch: On your iPhone, open the Watch app, go to My Watch > General > Software Update and install watchOS 10.6
  6. Verify the update was successful by checking the software version in Settings/General/About
Caveat Standard Apple update兼容性 considerations; ensure apps are compatible with the new OS versions before upgrading in production environments

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-40805 — 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-40805 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