IpadosOperating system · Apple

CVE-2024-40777

MEDIUM · 5.5 CVSS v3.1 Published 2024-07-29
Fix available
A fix is available. Upgrade to 1.3 / 10.6 or later.
See remediation →
58/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
An out-of-bounds access issue was addressed with improved bounds checking. This issue is fixed in iOS 17.6 and iPadOS 17.6, macOS Sonoma 14.6, tvOS 17.6, visionOS 1.3, watchOS 10.6. Processing a maliciously crafted file may lead to unexpected app termination.

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

An out-of-bounds access vulnerability in Apple's ecosystem (iOS, iPadOS, macOS, tvOS, visionOS, watchOS) that allows a maliciously crafted file to trigger improper memory access, leading to unexpected app termination due to insufficient bounds checking.

MitigationApply the available security updates (iOS 17.6, iPadOS 17.6, macOS Sonoma 14.6, tvOS 17.6, visionOS 1.3, watchOS 10.6) to all affected Apple devices within the organization.

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
VisionosOperating system
Affected:< 1.3
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
None
Integrity
None
Availability
High

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

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

  1. Check iOS version on iPhone
    Open Settings > General > About and look at the 'Version' field
    Affected if Version is less than 17.6 (for example, 17.5.x or earlier)
  2. Check iPadOS version on iPad
    Open Settings > General > About and look at the 'Version' field
    Affected if Version is less than 17.6 (for example, 17.5.x or earlier)
  3. Check macOS version on Mac
    Open System Settings > General > About (or Apple menu > About This Mac) and look at the 'macOS' version
    Affected if Version is 14.0 through 14.5.x (any version 14.0 or higher but below 14.6)
  4. Check tvOS version on Apple TV
    Open Settings > General > About > Version
    Affected if Version is less than 17.6 (for example, 17.5.x or earlier)
  5. Check visionOS version on Apple Vision Pro
    Open Settings > General > About and look at the version number
    Affected if Version is less than 1.3 (for example, 1.2.x or earlier)
  6. Check watchOS version on Apple Watch
    Open Settings > General > About on the watch, or open the Watch app on iPhone and go to My Watch > General > About
    Affected if Version is less than 10.6 (for example, 10.5.x or earlier)

The device is affected if it runs any version below the fixed release for its platform: iOS/iPadOS/tvOS/watchOS below 17.6, visionOS below 1.3, or macOS Sonoma between 14.0 and 14.5.x.

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 1.3 / 10.6 / 14.6 or later
Fixed in 1.310.614.6
Interim mitigation

Apply the available security updates (iOS 17.6, iPadOS 17.6, macOS Sonoma 14.6, tvOS 17.6, visionOS 1.3, watchOS 10.6) to all affected Apple devices within the organization.

Recommended fix High confidence

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

  1. For iOS/iPadOS devices: Back up the device, then go to Settings > General > Software Update and install iOS 17.6 or iPadOS 17.6
  2. For macOS devices: Back up the Mac, then go to System Settings > General > Software Update and install macOS Sonoma 14.6
  3. For Apple TV: Go to Settings > General > Software Update and install tvOS 17.6
  4. For Apple Vision Pro: Go to Settings > General > Software Update and install visionOS 1.3
  5. For Apple Watch: Ensure the watch is charging and connected to iPhone, then open the Watch app on iPhone, go to General > Software Update, and install watchOS 10.6

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

Fix this in Ipados 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-40777 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-40777 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