dbcve.org
IpadosOperating system · Apple

CVE-2024-27859

HIGH · 8.8 CVSS v3.1 Published 2025-02-10
Fix available
A fix is available. Upgrade to 1.1 / 10.4 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable 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
The issue was addressed with improved memory handling. This issue is fixed in iOS 17.4 and iPadOS 17.4, macOS Sonoma 14.4, tvOS 17.4, visionOS 1.1, watchOS 10.4. Processing web content may lead to 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

Memory corruption vulnerability in WebKit affecting iOS, iPadOS, macOS, tvOS, visionOS, and watchOS. Processing maliciously crafted web content triggers the memory handling flaw, enabling arbitrary code execution with the privileges of the WebKit process.

MitigationApply vendor-supplied OS updates: iOS 17.4+, iPadOS 17.4+, macOS Sonoma 14.4+, tvOS 17.4+, visionOS 1.1+, and watchOS 10.4+. Disable JavaScript in untrusted browsers as an interim workaround if updates cannot be immediately deployed.

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.4
Iphone OsOperating system
Affected:< 17.4
macOSOperating system
Affected:< 14.4
TvosOperating system
Affected:< 17.4
VisionosOperating system
Affected:< 1.1
WatchosOperating system
Affected:< 10.4

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 or iPadOS version
    Go to Settings > General > About on the device and note the version number displayed
    Affected if The version is earlier than 17.4 (for example, 17.3.1 or earlier)
  2. Check macOS version
    Click the Apple menu > About This Mac and note the version number shown under macOS
    Affected if The version is earlier than 14.4 (for example, 14.3.1 or earlier)
  3. Check tvOS version
    Go to Settings > General > About TV on Apple TV and note the version displayed
    Affected if The version is earlier than 17.4
  4. Check watchOS version
    Open the Watch app on paired iPhone, go to My Watch > General > About and note the watchOS version
    Affected if The version is earlier than 10.4
  5. Check visionOS version
    Go to Settings > General > About on Vision Pro and note the version number
    Affected if The version is earlier than 1.1

Your device is affected if its operating system version is below the patched release (iOS/iPadOS 17.4, macOS 14.4, tvOS 17.4, visionOS 1.1, or watchOS 10.4) and you use the browser or any app that embeds WebKit.

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.1 / 10.4 / 14.4 or later
Fixed in 1.110.414.4
Interim mitigation

Apply vendor-supplied OS updates: iOS 17.4+, iPadOS 17.4+, macOS Sonoma 14.4+, tvOS 17.4+, visionOS 1.1+, and watchOS 10.4+. Disable JavaScript in untrusted browsers as an interim workaround if updates cannot be immediately deployed.

Recommended fix High confidence

iOS 17.4, iPadOS 17.4, macOS Sonoma 14.4, tvOS 17.4, visionOS 1.1, watchOS 10.4

  1. For iPhone: Go to Settings > General > Software Update and install iOS 17.4
  2. For iPad: Go to Settings > General > Software Update and install iPadOS 17.4
  3. For Mac: Go to System Settings > General > Software Update and install macOS Sonoma 14.4
  4. For Apple TV: Go to Settings > System > Software Updates and install tvOS 17.4
  5. For Apple Watch: Go to Settings > General > Software Update on the paired iPhone, or go to Settings > General > Software Update on the watch itself, and install watchOS 10.4
  6. For Apple Vision Pro: Go to Settings > General > Software Update and install visionOS 1.1
  7. After updating, verify the update was successful by checking the version number in Settings > General > About
Caveat Standard Apple minor/major OS updates typically include compatibility checks; ensure dependent apps are compatible before updating

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

Fix this in Ipados Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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