dbcve.org
IpadosOperating system · Apple

CVE-2024-27802

HIGH · 7.8 CVSS v3.1 Published 2024-06-10
Fix available
A fix is available. Upgrade to 1.2 / 12.7.5 or later.
See remediation →
81/100
Remediation priority · High
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 read was addressed with improved input validation. This issue is fixed in iOS 16.7.8 and iPadOS 16.7.8, iOS 17.5 and iPadOS 17.5, macOS Monterey 12.7.5, macOS Sonoma 14.5, macOS Ventura 13.6.7, tvOS 17.5, visionOS 1.2. Processing a maliciously crafted file may lead to unexpected app termination or arbitrary code execution.

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 read vulnerability in Apple operating systems allows processing of maliciously crafted files to trigger memory corruption. The flaw exists in file parsing logic where insufficient bounds checking permits reading beyond allocated buffer boundaries, potentially enabling arbitrary code execution.

MitigationApply the available vendor patches by updating affected devices to iOS 16.7.8/17.5, iPadOS 16.7.8/17.5, macOS 12.7.5/13.6.7/14.5, tvOS 17.5, or visionOS 1.2 as appropriate. Restrict processing of untrusted file types until patches are applied.

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:< 16.7.8>= 17.0, < 17.5
Iphone OsOperating system
Affected:< 16.7.8>= 17.0, < 17.5
macOSOperating system
Affected:< 12.7.5>= 13.0, < 13.6.7>= 14.0, < 14.5
TvosOperating system
Affected:< 17.5
VisionosOperating system
Affected:< 1.2

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
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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
    Go to Settings > General > About on the iPhone. Note the version number displayed next to 'Version'.
    Affected if The version is earlier than 16.7.8, or falls between 17.0 and 17.5 (exclusive).
  2. Check iPadOS version
    Go to Settings > General > About on the iPad. Note the version number displayed next to 'Version'.
    Affected if The version is earlier than 16.7.8, or falls between 17.0 and 17.5 (exclusive).
  3. Check macOS version
    Click the Apple menu > About This Mac. Note the version number (such as 14.4 or 13.5).
    Affected if The version is earlier than 12.7.5; or falls between 13.0 and 13.6.7 (exclusive); or falls between 14.0 and 14.5 (exclusive).
  4. Check tvOS version
    Go to Settings > General > About > Version on Apple TV.
    Affected if The version is earlier than 17.5.
  5. Check visionOS version
    Go to Settings > General > About on Apple Vision Pro. Note the version number.
    Affected if The version is earlier than 1.2.

The device is affected if its installed OS version falls within any of the vulnerable version ranges listed for the respective Apple platform.

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.2 / 12.7.5 / 13.6.7 or later
Fixed in 1.212.7.513.6.7
Interim mitigation

Apply the available vendor patches by updating affected devices to iOS 16.7.8/17.5, iPadOS 16.7.8/17.5, macOS 12.7.5/13.6.7/14.5, tvOS 17.5, or visionOS 1.2 as appropriate. Restrict processing of untrusted file types until patches are applied.

Recommended fix High confidence

iOS 16.7.8 or iOS 17.5 (iPhone), iPadOS 16.7.8 or iPadOS 17.5 (iPad), macOS 12.7.5/13.6.7/14.5 depending on Mac model, tvOS 17.5, visionOS 1.2

  1. Identify your current device OS version in Settings > General > About (iOS/iPadOS) or System Preferences > General > Software Update (macOS)
  2. Navigate to Settings > General > Software Update (iOS/iPadOS) or System Preferences > Software Update (macOS) to check for available updates
  3. Download and install the appropriate security update: iOS 16.7.8 or iOS 17.5 (iPhone), iPadOS 16.7.8 or iPadOS 17.5 (iPad), macOS 12.7.5 (Monterey), macOS 13.6.7 (Ventura), or macOS 14.5 (Sonoma)
  4. For tvOS devices, go to Settings > System > Software Update and install tvOS 17.5
  5. For Vision Pro, go to Settings > General > Software Update and install visionOS 1.2
  6. Restart the device after installation to ensure the security patch is fully applied
Caveat Ensure device meets minimum requirements for the target OS version; some older devices may only support 16.7.x and not 17.x

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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