dbcve.org
SafariWeb browser · Apple

CVE-2024-27834

MEDIUM · 5.5 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 2.44.2 / 10.5 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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, watchOS 10.5. An attacker with arbitrary read and write capability may be able to bypass Pointer Authentication.

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

Pointer Authentication (PAC) bypass vulnerability in Apple's operating systems. An attacker with arbitrary read/write capability can bypass PAC checks, which are cryptographic protections on pointer integrity, potentially enabling further exploitation of memory corruption vulnerabilities.

MitigationApply the relevant security updates: Safari 17.5, iOS/iPadOS 16.7.8 or 17.5, macOS Sonoma 14.5, tvOS 17.5, or watchOS 10.5 depending on the affected platform.

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
FedoraOperating system
Affected:= 39= 40
IpadosOperating system
Affected:< 17.5
Iphone OsOperating system
Affected:< 17.5
macOSOperating system
Affected:>= 14.0, < 14.5
TvosOperating system
Affected:< 17.5
WatchosOperating system
Affected:< 10.5
WebkitgtkWeb browser
Affected:< 2.44.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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 platform and OS version
    On macOS: use 'sw_vers -productVersion' in terminal, or Apple menu > About This Mac. On iOS/iPadOS: Settings > General > About. On tvOS/watchOS: Settings > General > About.
    Affected if The OS version is < 17.5 for iOS/iPadOS/tvOS/watchOS, or >= 14.0 but < 14.5 for macOS Sonoma.
  2. Check Safari browser version
    Open Safari, then Safari > About Safari (on macOS) or Settings > Safari > About (on iOS).
    Affected if Safari version is < 17.5 on any platform.
  3. Verify WebKitGTK library version on Linux
    Run 'pkg-config --modversion webkit2gtk-4.1' or 'pkg-config --modversion webkit2gtk-4.0' depending on the API version in use.
    Affected if The WebKitGTK library version is < 2.44.2.
  4. Check Fedora Linux WebKitGTK package
    Run 'rpm -qa | grep webkit2gtk' on Fedora to list the installed webkit2gtk package version.
    Affected if The installed webkit2gtk package version is < 2.44.2 on Fedora 39 or 40.

You are affected if your Safari is below 17.5, your iOS/iPadOS/tvOS/watchOS is below 17.5, your macOS is between 14.0 and 14.4, your watchOS is below 10.5, or your WebKitGTK is below 2.44.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 2.44.2 / 10.5 / 14.5 or later
Fixed in 2.44.210.514.5
Interim mitigation

Apply the relevant security updates: Safari 17.5, iOS/iPadOS 16.7.8 or 17.5, macOS Sonoma 14.5, tvOS 17.5, or watchOS 10.5 depending on the affected platform.

Recommended fix High confidence

Upgrade to Safari 17.5, iOS/iPadOS 17.5 or 16.7.8, macOS 14.5, tvOS 17.5, watchOS 10.5, or WebKitGTK 2.44.2+

  1. Upgrade Safari to version 17.5 or later
  2. Upgrade iOS devices to version 17.5 (or 16.7.8 for older devices)
  3. Upgrade iPadOS to version 17.5 (or 16.7.8 for older devices)
  4. Upgrade macOS Sonoma (14.x) to version 14.5
  5. Upgrade tvOS to version 17.5
  6. Upgrade watchOS to version 10.5
  7. For WebKitGTK-based browsers, upgrade to version 2.44.2 or later
  8. For Fedora systems, apply the webkit2gtk security update when available via dnf update
Caveat Major OS version upgrades (e.g., iOS 16 to 17) may have feature changes or app compatibility considerations; always review release notes before upgrading production devices

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

Fix this in Safari Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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