CVE-2025-24237
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 · uneditedA buffer overflow was addressed with improved bounds checking. This issue is fixed in iOS 18.4 and iPadOS 18.4, iPadOS 17.7.6, macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, visionOS 2.4, watchOS 11.4. An app may be able to cause unexpected system termination.
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 confidenceBuffer overflow vulnerability in an Apple system component affecting iOS, iPadOS, macOS, visionOS, and watchOS. The issue was addressed with improved bounds checking. The vulnerability allows a malicious app to cause unexpected system termination (denial of service).
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.7.6>= 18.0, < 18.4< 18.4>= 13.0, < 13.7.5>= 14.0, < 14.7.5>= 15.0, < 15.4< 2.4CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check iPhone or iPad OS versionOn the device, go to Settings > General > About and note the version number displayed next to 'Version'Affected if The version is less than 18.4 for iOS, or less than 17.7.6 OR between 18.0 and 18.4 for iPadOS
-
Check macOS versionClick the Apple menu > About This Mac and note the version number shown (such as 13.x, 14.x, or 15.x)Affected if The version is 13.0 to 13.7.4, 14.0 to 14.7.4, or 15.0 to 15.3 (meaning less than the 13.7.5, 14.7.5, or 15.4 security updates)
-
Check visionOS versionOn Apple Vision, go to Settings > General > About and locate the version numberAffected if The version is less than 2.4
-
Confirm vulnerability scopeThis is a buffer overflow in core operating system components - no specific feature, configuration, or module needs to be enabled for the flaw to existAffected if The device runs any affected OS version listed above and has not applied the vendor security update
A user is affected if their device runs iOS/iPadOS below 18.4 (or below 17.7.6 for iPadOS 17), macOS below 13.7.5/14.7.5/15.4, or visionOS below 2.4.
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 · scoped2.413.7.514.7.5
Apply the security updates: iOS 18.4, iPadOS 18.4/17.7.6, macOS Sequoia 15.4, Sonoma 14.7.5, Ventura 13.7.5, visionOS 2.4, or watchOS 11.4 depending on affected devices in the environment.
iOS 18.4, iPadOS 18.4, iPadOS 17.7.6, macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, visionOS 2.4, watchOS 11.4
- Identify the Apple device type (iPhone, iPad, Mac, Apple Vision Pro, or Apple Watch)
- Check the current operating system version in Settings > General > About (iOS/iPadOS) or System Settings > General > About (macOS)
- For iPhone/iPad: Navigate to Settings > General > Software Update and install the appropriate update (iOS 18.4, iPadOS 18.4, or iPadOS 17.7.6)
- For Mac: Open System Settings > General > Software Update and install macOS 15.4 (Sequoia), 14.7.5 (Sonoma), or 13.7.5 (Ventura) depending on your current macOS version
- For Apple Vision Pro: Go to Settings > General > Software Update and install visionOS 2.4
- For Apple Watch: Open the Watch app on iPhone, go to My Watch > General > Software Update and install watchOS 11.4
- After updating, verify the new version is installed by checking Settings > General > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-24237 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-24237 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