dbcve.org
IpadosOperating system · Apple

CVE-2024-27857

HIGH · 7.8 CVSS v3.1 Published 2024-06-10
Fix available
A fix is available. Upgrade to 1.2 / 14.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 access issue was addressed with improved bounds checking. This issue is fixed in iOS 17.5 and iPadOS 17.5, macOS Sonoma 14.5, tvOS 17.5, visionOS 1.2. A remote attacker may be able to cause 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 · moderate confidence

An out-of-bounds memory access vulnerability in multiple Apple operating systems (iOS, iPadOS, macOS, tvOS, visionOS) that was addressed with improved bounds checking. A remote attacker can exploit this to cause app termination or achieve arbitrary code execution, likely through maliciously crafted web content or network-based vectors.

MitigationApply the vendor-supplied patches by updating all affected devices to iOS 17.5, iPadOS 17.5, macOS Sonoma 14.5, tvOS 17.5, or visionOS 1.2. For enterprise environments, utilize mobile device management (MDM) or patch management tools to ensure complete coverage.

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.5
Iphone OsOperating system
Affected:< 17.5
macOSOperating system
Affected:>= 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. Identify your Apple operating system
    Determine which Apple OS is running on the device: iOS (iPhone), iPadOS (iPad), macOS (Mac), tvOS (Apple TV), or visionOS (Apple Vision Pro)
    Affected if The device runs any of these Apple operating systems
  2. Check iOS or iPadOS version
    On iPhone or iPad, go to Settings > General > About > Version to view the installed version number
    Affected if Running iOS or iPadOS version lower than 17.5 (e.g., 17.4.x, 17.3.x, etc.)
  3. Check macOS version
    On Mac, go to System Settings (or System Preferences on older versions) > About > Version to view the installed version number
    Affected if Running macOS Sonoma version 14.0 through 14.4 (versions 14.0, 14.1, 14.2, 14.3, or 14.4)
  4. Check tvOS version
    On Apple TV, go to Settings > General > About > Version to view the installed version number
    Affected if Running tvOS version lower than 17.5 (e.g., 17.4.x, 17.3.x, etc.)
  5. Check visionOS version
    On Apple Vision Pro, go to Settings > About > Version to view the installed version number
    Affected if Running visionOS version lower than 1.2 (e.g., 1.1.x, 1.0.x, etc.)

You are affected if your device runs any of these Apple operating systems at a version lower than the fixed release (iOS/iPadOS/tvOS below 17.5, macOS Sonoma below 14.5, or visionOS below 1.2).

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 / 14.5 / 17.5 or later
Fixed in 1.214.517.5
Interim mitigation

Apply the vendor-supplied patches by updating all affected devices to iOS 17.5, iPadOS 17.5, macOS Sonoma 14.5, tvOS 17.5, or visionOS 1.2. For enterprise environments, utilize mobile device management (MDM) or patch management tools to ensure complete coverage.

Recommended fix High confidence

iOS 17.5 / iPadOS 17.5 / macOS Sonoma 14.5 / tvOS 17.5 / visionOS 1.2

  1. For iPhone users: Upgrade to iOS 17.5 via Settings > General > Software Update
  2. For iPad users: Upgrade to iPadOS 17.5 via Settings > General > Software Update
  3. For Mac users: Upgrade to macOS Sonoma 14.5 via System Settings > General > Software Update
  4. For Apple TV users: Upgrade to tvOS 17.5 via Settings > General > Apple TV Software Updates
  5. For Apple Vision users: Upgrade to visionOS 1.2 via Settings > General > Software Update

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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