dbcve.org
SafariWeb browser · Apple

CVE-2024-44192

MEDIUM · 5.5 CVSS v3.1 Published 2025-03-10
Fix available
A fix is available. Upgrade to 2.0 / 11.0 or later.
See remediation →
58/100
Remediation priority · Elevated
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 18, iOS 18 and iPadOS 18, macOS Sequoia 15, tvOS 18, visionOS 2, watchOS 11. Processing maliciously crafted web content may lead to an unexpected process crash.

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

This is a memory safety issue in web content processing within Safari and WebKit components across Apple's ecosystem. Processing maliciously crafted web content triggers an unexpected process crash due to improper bounds or validity checks that were not properly enforced.

MitigationUpdate all affected Apple devices to the fixed versions: Safari 18, iOS 18/iPadOS 18, macOS Sequoia 15, tvOS 18, visionOS 2, or watchOS 11.

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:< 18.0
Iphone OsOperating system
Affected:< 18.0
macOSOperating system
Affected:< 15.0
TvosOperating system
Affected:< 18.0
VisionosOperating system
Affected:< 2.0
WatchosOperating system
Affected:< 11.0

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 menu > About Safari, or use menu bar: Safari > About Safari. The version number is displayed.
    Affected if The version shown is earlier than 18.0 (for example, 17.x or earlier)
  2. Check macOS version
    Click Apple menu > About This Mac. The macOS version is displayed (for example, Sonoma 14, Ventura 13, etc.).
    Affected if The macOS version is earlier than 15.0 (macOS Sequoia). Note: Safari bundled with macOS versions below 15 is affected regardless of Safari's standalone version.
  3. Check iOS/iPadOS version on iPhone or iPad
    Go to Settings > General > About. The iOS version is displayed.
    Affected if The iOS/iPadOS version is earlier than 18.0 (for example, 17.x or earlier)
  4. Check tvOS version on Apple TV
    Go to Settings > General > About TV > Version.
    Affected if The tvOS version is earlier than 18.0
  5. Check visionOS version on Apple Vision Pro
    Go to Settings > General > About > visionOS Version.
    Affected if The visionOS version is earlier than 2.0
  6. Check watchOS version on Apple Watch
    On iPhone, open Watch app, go to My Watch > General > About. Or on Apple Watch, go to Settings > General > About.
    Affected if The watchOS version is earlier than 11.0

You are affected if any device runs Safari, iOS, macOS, tvOS, visionOS, or watchOS with a version number lower than the fixed versions (18.0 for Safari/iOS/tvOS, 15.0 for macOS, 2.0 for visionOS, 11.0 for watchOS).

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.0 / 11.0 / 15.0 or later
Fixed in 2.011.015.0
Interim mitigation

Update all affected Apple devices to the fixed versions: Safari 18, iOS 18/iPadOS 18, macOS Sequoia 15, tvOS 18, visionOS 2, or watchOS 11.

Recommended fix High confidence

iOS 18 / iPadOS 18, macOS Sequoia 15, watchOS 11, tvOS 18, visionOS 2, Safari 18

  1. Ensure your device is connected to the internet and has sufficient battery or is plugged into power
  2. For iPhone/iPad: Go to Settings > General > Software Update and install iOS 18 or iPadOS 18
  3. For Mac: Go to System Settings > General > Software Update and install macOS Sequoia 15
  4. For Apple Watch: Open the Watch app on iPhone, go to General > Software Update, and install watchOS 11
  5. For Apple TV: Go to Settings > System > Software Updates and install tvOS 18
  6. For Vision Pro: Go to Settings > General > Software Update and install visionOS 2
  7. For Safari: Update via the macOS Sequoia 15 update or download Safari 18 from Apple's website if available separately
Caveat Apple major OS updates may have compatibility issues with older applications; review app compatibility before updating

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-44192 — 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-44192 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