dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 12 Dec 2024.
Debian LinuxOperating system · Debian

CVE-2024-44308

HIGH · 8.8 CVSS v3.1 Published 2024-11-20
Fix available
A fix is available. Upgrade to 2.1.1 / 15.1.1 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild 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
The issue was addressed with improved checks. This issue is fixed in Safari 18.1.1, iOS 17.7.2 and iPadOS 17.7.2, iOS 18.1.1 and iPadOS 18.1.1, macOS Sequoia 15.1.1, visionOS 2.1.1. Processing maliciously crafted web content may lead to arbitrary code execution. Apple is aware of a report that this issue may have been actively exploited on Intel-based Mac systems.

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 vulnerability allowing arbitrary code execution when processing maliciously crafted web content. The issue was addressed with improved checks. This is a client-side code execution flaw affecting Safari and WebKit-based applications across iOS, iPadOS, macOS, and visionOS devices.

MitigationApply the vendor-supplied updates: Safari 18.1.1, iOS/iPadOS 17.7.2, iOS/iPadOS 18.1.1, macOS Sequoia 15.1.1, or visionOS 2.1.1. Prioritize Intel-based Mac systems given reported active exploitation.

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
Debian LinuxOperating system
Affected:= 11.0
SafariWeb browser
Affected:< 18.1.1
IpadosOperating system
Affected:< 17.7.2>= 18.0, < 18.1.1
Iphone OsOperating system
Affected:< 17.7.2>= 18.0, < 18.1.1
macOSOperating system
Affected:>= 15.0, < 15.1.1
VisionosOperating system
Affected:< 2.1.1

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. Check Safari version on macOS
    Open Safari, then go to Safari menu > About Safari. The version number is displayed in the pop-up window.
    Affected if Safari version is earlier than 18.1.1 on macOS
  2. Check iOS or iPadOS version and Safari
    Go to Settings > General > Software Update to see iOS/iPadOS version. For Safari version, go to Settings > Safari > About.
    Affected if iOS/iPadOS version is earlier than 17.7.2, or is 18.0 through 18.1.1 (meaning version is less than 18.1.1)
  3. Check visionOS version
    Go to Settings > General > Software Update to see visionOS version. For Safari version, go to Settings > Safari > About.
    Affected if visionOS version is earlier than 2.1.1
  4. Check for WebKit on Debian Linux
    Run command: dpkg -l | grep -i webkit or rpm -qa | grep -i webkit to list installed WebKit packages.
    Affected if Running Debian 11.0 with WebKit packages that have not been updated to address this vulnerability (the specific package versions are not enumerated in the CVE data)

You are affected if your Safari version is below 18.1.1, your iOS/iPadOS is below 17.7.2 or between 18.0 and 18.1.1, your visionOS is below 2.1.1, or you are on Debian 11.0 with an unpatched WebKit installation, AND you use WebKit/Safari to browse web content (which is the default and typical usage).

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.1.1 / 15.1.1 / 17.7.2 or later
Fixed in 2.1.115.1.117.7.2
Interim mitigation

Apply the vendor-supplied updates: Safari 18.1.1, iOS/iPadOS 17.7.2, iOS/iPadOS 18.1.1, macOS Sequoia 15.1.1, or visionOS 2.1.1. Prioritize Intel-based Mac systems given reported active exploitation.

Recommended fix High confidence

Safari 18.1.1, iOS 17.7.2/18.1.1, iPadOS 17.7.2/18.1.1, macOS Sequoia 15.1.1, visionOS 2.1.1

  1. For Safari: Update to Safari 18.1.1 via macOS system software update or download from apple.com
  2. For iPhone: Go to Settings > General > Software Update and update to iOS 18.1.1 (or iOS 17.7.2 if staying on iOS 17)
  3. For iPad: Go to Settings > General > Software Update and update to iPadOS 18.1.1 (or iPadOS 17.7.2 if staying on iPadOS 17)
  4. For macOS Sequoia: Go to System Settings > General > Software Update and update to macOS Sequoia 15.1.1
  5. For visionOS: Go to Settings > General > Software Update and update to visionOS 2.1.1
  6. Debian 11.0: Check for WebKitGTK or WebKit2GTK security updates via 'apt update && apt upgrade' or apply Debian security patches
Caveat Standard minor OS/browser updates typically preserve compatibility; no major API changes expected in these point releases

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

Fix this in Debian Linux Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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