SafariWeb browser · Apple

CVE-2024-27856

HIGH · 7.8 CVSS v3.1 Published 2025-01-15
Fix available
A fix is available. Upgrade to 1.2 / 10.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
The issue was addressed with improved checks. This issue is fixed in Safari 17.5, iOS 16.7.8 and iPadOS 16.7.8, iOS 17.5 and iPadOS 17.5, macOS Sonoma 14.5, tvOS 17.5, visionOS 1.2, watchOS 10.5. Processing a 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 · moderate confidence

A file processing vulnerability in multiple Apple platforms (Safari, iOS, iPadOS, macOS, tvOS, visionOS, watchOS) allows processing of a specially crafted file to cause app termination or execute arbitrary code, likely due to insufficient input validation checks.

MitigationApply the vendor-supplied patches: update to Safari 17.5, iOS/iPadOS 16.7.8 or 17.5, macOS Sonoma 14.5, tvOS 17.5, visionOS 1.2, or watchOS 10.5 as appropriate for affected systems.

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
SafariWeb browser
Affected:< 17.5
IpadosOperating system
Affected:< 16.7.8>= 17.0, < 17.5
Iphone OsOperating system
Affected:< 16.7.8>= 17.0, < 17.5
macOSOperating system
Affected:< 14.5
TvosOperating system
Affected:< 17.5
VisionosOperating system
Affected:< 1.2
WatchosOperating system
Affected:< 10.5

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 Safari version on macOS
    Open Safari, go to Safari > About Safari or visit the URL 'safari://' to view the version number
    Affected if Version is lower than 17.5 on macOS
  2. Check iOS version on iPhone or iPad
    Go to Settings > General > About to view the iOS version number
    Affected if Version is lower than 16.7.8, or between 17.0 and 17.4 (inclusive)
  3. Check macOS version
    Go to System Settings > About or run 'sw_vers' in Terminal to view the macOS version
    Affected if Version is lower than 14.5 (Sonoma)
  4. Check tvOS version on Apple TV
    Go to Settings > General > About to view the tvOS version number
    Affected if Version is lower than 17.5
  5. Check visionOS version on Apple Vision Pro
    Go to Settings > About to view the visionOS version number
    Affected if Version is lower than 1.2
  6. Check watchOS version on Apple Watch
    Open the Watch app on iPhone, go to My Watch > General > About to view watchOS version
    Affected if Version is lower than 10.5

If any of the above installed product versions fall within the affected ranges, the environment is potentially vulnerable when processing specially crafted files.

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

Apply the vendor-supplied patches: update to Safari 17.5, iOS/iPadOS 16.7.8 or 17.5, macOS Sonoma 14.5, tvOS 17.5, visionOS 1.2, or watchOS 10.5 as appropriate for affected systems.

Recommended fix High confidence

macOS Sonoma 14.5 | iOS/iPadOS 17.5 | iOS/iPadOS 16.7.8 | Safari 17.5 | tvOS 17.5 | visionOS 1.2 | watchOS 10.5

  1. Identify the Apple device and current operating system version (Settings > General > About on iOS/iPadOS, System Settings or System Preferences > General > About on macOS)
  2. Determine the appropriate fixed version based on your current OS: For iOS/iPadOS 16.x devices, upgrade to 16.7.8; For iOS/iPadOS 17.x devices, upgrade to 17.5; For macOS devices, upgrade to 14.5 (Sonoma); For Safari (standalone), upgrade to 17.5; For tvOS devices, upgrade to 17.5; For visionOS devices, upgrade to 1.2; For watchOS devices, upgrade to 10.5
  3. Open Settings > General > Software Update on iOS/iPadOS/watchOS/tvOS/visionOS, or System Settings > Software Update on macOS
  4. Download and install the available security update
  5. Verify the update was successful by checking the new version number in Settings/About

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

Fix this in Safari 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-27856 — 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-27856 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