CVE-2024-27800
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 · uneditedThis issue was addressed by removing the vulnerable code. This issue is fixed in iOS 16.7.8 and iPadOS 16.7.8, iOS 17.5 and iPadOS 17.5, macOS Monterey 12.7.5, macOS Sonoma 14.5, macOS Ventura 13.6.7, tvOS 17.5, visionOS 1.2, watchOS 10.5. Processing a maliciously crafted message may lead to a denial-of-service.
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 confidenceA denial-of-service vulnerability exists in message processing across multiple Apple platforms (iOS, iPadOS, macOS, tvOS, visionOS, watchOS). The vulnerability is triggered by processing a maliciously crafted message, and was remediated by removing the vulnerable code rather than patching it.
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< 16.7.8>= 17.0, < 17.5< 16.7.8>= 17.0, < 17.5< 12.7.5>= 13.0, < 13.6.7>= 14.0, < 14.5< 17.5< 1.2< 10.5CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/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.
-
Check iOS version on iPhoneGo to Settings > General > About on the iPhone and note the version numberAffected if Version is less than 16.7.8, or between 17.0 and 17.4 (inclusive)
-
Check iPadOS version on iPadGo to Settings > General > About on the iPad and note the version numberAffected if Version is less than 16.7.8, or between 17.0 and 17.4 (inclusive)
-
Check macOS version on MacClick Apple menu > About This Mac and note the version numberAffected if Version is less than 12.7.5, between 13.0 and 13.6.6, or between 14.0 and 14.4 (inclusive)
-
Check tvOS version on Apple TVGo to Settings > General > About > Version on Apple TVAffected if Version is less than 17.5
-
Check visionOS version on Vision ProGo to Settings > General > About on Vision Pro deviceAffected if Version is less than 1.2
-
Check watchOS version on Apple WatchOpen the Watch app on iPhone, go to My Watch > General > About, or on Apple Watch go to Settings > General > AboutAffected if Version is less than 10.5
If any Apple device runs an affected version as listed above, it is vulnerable to the CVE-2024-27800 message processing denial-of-service flaw.
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.210.512.7.5
Apply the relevant security update for the affected Apple platform version: iOS 16.7.8/17.5, iPadOS 16.7.8/17.5, macOS 12.7.5/13.6.7/14.5, tvOS 17.5, visionOS 1.2, or watchOS 10.5.
iOS 16.7.8 or iOS 17.5 / iPadOS 16.7.8 or iPadOS 17.5 / macOS 12.7.5, 13.6.7, or 14.5 / tvOS 17.5 / visionOS 1.2 / watchOS 10.5 (depending on device and starting version)
- Identify the current installed version of the affected Apple operating system on the device
- For iPhone or iPad: Go to Settings > General > Software Update and install the recommended update (iOS 16.7.8 or iOS 17.5, iPadOS 16.7.8 or iPadOS 17.5)
- For Mac: Go to System Settings > General > Software Update and install the recommended update (macOS 12.7.5, 13.6.7, or 14.5)
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 17.5
- For Apple Watch: Go to Settings > General > Software Update and install watchOS 10.5
- For Apple Vision Pro: Go to Settings > General > Software Update and install visionOS 1.2
- 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.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27800 — 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
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- seclists.org
- support.apple.com
- support.apple.com
- 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-27800 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