CVE-2024-40780
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 · uneditedAn out-of-bounds read was addressed with improved bounds checking. This issue is fixed in Safari 17.6, iOS 16.7.9 and iPadOS 16.7.9, iOS 17.6 and iPadOS 17.6, macOS Sonoma 14.6, tvOS 17.6, visionOS 1.3, watchOS 10.6. 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 · high confidenceAn out-of-bounds read vulnerability in WebKit (Safari's rendering engine) allows maliciously crafted web content to trigger an unexpected process crash. The issue was addressed with improved bounds checking in the affected Apple operating systems and browsers.
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< 17.6< 16.7.9>= 17.0, < 17.6< 16.7.9>= 17.0, < 17.6< 10.6< 17.6< 1.3< 14.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify your Apple platform and Safari/ browser versionOn iPhone/iPad: go to Settings > General > About to see iOS/iPadOS version; On Mac: open Safari, click Safari > About Safari to see version; On Apple Watch: open Settings > General > About; On Apple TV: go to Settings > General > About; On Vision Pro: go to Settings > General > AboutAffected if The installed version falls below the fixed versions (Safari < 17.6, iOS/iPadOS < 16.7.9 or >= 17.0 but < 17.6, macOS < 14.6, watchOS < 10.6, tvOS < 17.6, visionOS < 1.3)
-
Confirm WebKit is in useThis vulnerability affects WebKit, which powers Safari and all in-app browsers on iOS/iPadOS. Any use of Safari or apps that render web content on the affected device triggers the vulnerable code pathAffected if Safari or any WebKit-based browser is used on the device
-
Compare your version to the affected rangesManually compare the version number found in step 1 against: Safari < 17.6; iOS/iPadOS < 16.7.9 OR >= 17.0 and < 17.6; macOS < 14.6; watchOS < 10.6; tvOS < 17.6; visionOS < 1.3Affected if Your version matches any of the affected ranges listed
You are affected if your Safari or Apple OS version is lower than the fixed versions and you use Safari or WebKit-based browsers to view web content.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.310.614.6
Apply the available vendor patches by updating Safari to version 17.6, iOS/iPadOS to 16.7.9 or 17.6, macOS to Sonoma 14.6, tvOS to 17.6, visionOS to 1.3, and watchOS to 10.6. Alternatively, restrict user access to untrusted websites until patches are applied.
Safari 17.6 | iOS 16.7.9/17.6 | iPadOS 16.7.9/17.6 | macOS Sonoma 14.6 | tvOS 17.6 | visionOS 1.3 | watchOS 10.6
- For iPhone/iPad: Go to Settings > General > Software Update and install iOS/iPadOS 17.6 (or 16.7.9 for older devices)
- For Mac: Open System Settings > General > Software Update and install macOS Sonoma 14.6
- For Apple Watch: Open the Watch app on iPhone, go to General > Software Update, and install watchOS 10.6
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 17.6
- For Apple Vision Pro: Go to Settings > General > Software Update and install visionOS 1.3
- For Safari (if standalone): Ensure Safari is updated via macOS Sonoma 14.6 update or download Safari 17.6
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-40780 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sources- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- lists.debian.org
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-40780 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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