dbcve.org
SafariWeb browser · Apple

CVE-2024-44206

CRITICAL · 9.3 CVSS v3.1 Published 2024-10-24
Fix available
A fix is available. Upgrade to 1.3 / 14.6 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
An issue in the handling of URL protocols was addressed with improved logic. This issue is fixed in Safari 17.6, iOS 17.6 and iPadOS 17.6, macOS Sonoma 14.6, tvOS 17.6, visionOS 1.3, watchOS 10.6. A user may be able to bypass some web content restrictions.

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

This vulnerability in Apple's URL protocol handling allows users to bypass web content restrictions. The flaw was in the logic that controls how web content policies are enforced, potentially letting malicious pages circumvent security controls. It affects multiple Apple operating systems and browsers.

MitigationUpdate all affected Apple devices to the patched versions (Safari 17.6, iOS/iPadOS 17.6, macOS Sonoma 14.6, tvOS 17.6, visionOS 1.3, watchOS 10.6) to remediate this vulnerability.

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.6
IpadosOperating system
Affected:< 17.6
Iphone OsOperating system
Affected:< 17.6
macOSOperating system
Affected:< 14.6
TvosOperating system
Affected:< 17.6
VisionosOperating system
Affected:< 1.3

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
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/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. Check Safari version on macOS
    Open Safari, click Safari > About Safari to view the version number
    Affected if Version is earlier than 17.6 and web content restrictions are configured
  2. Check macOS version
    Click Apple menu > About This Mac to view the macOS version
    Affected if Version is earlier than 14.6 (Sonoma) and web content restrictions are in use
  3. Check iOS version on iPhone
    Go to Settings > General > About to view iOS version
    Affected if Version is earlier than 17.6 and content restrictions are enabled in Screen Time
  4. Check iPadOS version on iPad
    Go to Settings > General > About to view iPadOS version
    Affected if Version is earlier than 17.6 and content restrictions are enabled in Screen Time
  5. Check tvOS version on Apple TV
    Go to Settings > General > About to view tvOS version
    Affected if Version is earlier than 17.6 and content restrictions are configured

You are affected if any Apple device runs a version lower than the patched releases AND has web content restrictions or Screen Time controls 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.3 / 14.6 / 17.6 or later
Fixed in 1.314.617.6
Interim mitigation

Update all affected Apple devices to the patched versions (Safari 17.6, iOS/iPadOS 17.6, macOS Sonoma 14.6, tvOS 17.6, visionOS 1.3, watchOS 10.6) to remediate this vulnerability.

Recommended fix High confidence

iOS 17.6, iPadOS 17.6, macOS Sonoma 14.6, tvOS 17.6, visionOS 1.3, Safari 17.6

  1. Identify the Apple device and current operating system version (iOS, iPadOS, macOS, tvOS, visionOS, or Safari)
  2. For iOS/iPadOS devices: Navigate to Settings > General > Software Update and install iOS/iPadOS 17.6 or later
  3. For macOS devices: Open System Settings > General > Software Update and install macOS Sonoma 14.6 or later
  4. For Apple TV: Go to Settings > System > Software Updates and install tvOS 17.6 or later
  5. For Apple Vision Pro: Go to Settings > General > Software Update and install visionOS 1.3 or later
  6. For Safari (if standalone): Ensure the browser is updated via macOS update to Safari 17.6
  7. Verify the update was successful by checking the operating system or Safari version
Caveat Standard Apple minor/major OS updates may have app compatibility considerations; test critical web applications after updating

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

Fix this in Safari Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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