dbcve.org
SafariWeb browser · Apple

CVE-2024-27833

HIGH · 8.8 CVSS v3.1 Published 2024-06-10
Fix available
A fix is available. Upgrade to 1.2 / 16.7.8 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
An integer overflow was addressed with improved input validation. This issue is fixed in Safari 17.5, iOS 16.7.8 and iPadOS 16.7.8, iOS 17.5 and iPadOS 17.5, tvOS 17.5, visionOS 1.2. Processing maliciously crafted 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 · high confidence

A webkit integer overflow vulnerability that can be triggered by processing maliciously crafted web content, leading to arbitrary code execution. The fix implements improved input validation.

MitigationApply the available vendor patches by updating Safari to 17.5 and iOS/iPadOS to 16.7.8 or 17.5 (and corresponding tvOS/visionOS versions) on all affected devices.

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
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
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. Identify the Apple platform and Safari version
    On macOS, open Safari > Safari menu > About Safari to see the version number. On iOS/iPadOS, go to Settings > Safari (or Settings > General > About for iOS version). On Apple TV, go to Settings > General > About. On Vision Pro, go to Settings > General > About.
    Affected if Safari version is below 17.5, or iOS/iPadOS version is below 16.7.8 or between 17.0 and 17.4, or tvOS version is below 17.5, or visionOS version is below 1.2
  2. Confirm WebKit engine is in use
    The vulnerability exists in the WebKit rendering engine. Verify Safari is the default browser or that WebKit-based browsers are in use. On iOS/iPadOS, Safari and all third-party browsers must use WebKit by design.
    Affected if Using Safari or any WebKit-based browser on an affected OS version
  3. Check if JavaScript is enabled
    The vulnerability is triggered by processing malicious web content. Verify JavaScript status: In Safari, check Preferences > Security > Enable JavaScript. On iOS, Settings > Safari > Advanced > JavaScript should be noted (JavaScript is enabled by default).
    Affected if JavaScript is enabled (this is the default and required state for the exploit to trigger)

You are affected if Safari is below 17.5, or iOS/iPadOS is below 16.7.8 or between 17.0 and 17.4, or tvOS is below 17.5, or visionOS is below 1.2, and you use Safari or WebKit-based browsers with JavaScript enabled.

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

Apply the available vendor patches by updating Safari to 17.5 and iOS/iPadOS to 16.7.8 or 17.5 (and corresponding tvOS/visionOS versions) on all affected devices.

Recommended fix High confidence

Upgrade to Safari 17.5, iOS 16.7.8/iPadOS 16.7.8, iOS 17.5/iPadOS 17.5, tvOS 17.5, or visionOS 1.2 as applicable

  1. Identify the affected Apple product (Safari, iOS, iPadOS, tvOS, or visionOS) and current version
  2. For Safari on macOS: Open the App Store, click Updates, and install Safari 17.5
  3. For iOS/iPadOS devices: Go to Settings > General > Software Update and install the update (iOS 16.7.8 or iOS 17.5/iPadOS 16.7.8 or iPadOS 17.5 depending on device)
  4. For tvOS: Go to Settings > System > Software Updates and install tvOS 17.5
  5. For visionOS: Go to Settings > General > Software Update and install visionOS 1.2
  6. After updating, verify the version by checking Settings > General > About (or Safari > About Safari)
Caveat Apple security updates typically have minimal breaking changes; however, some legacy features may be deprecated in older iOS versions receiving backported patches

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

Fix this in Safari Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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