CVE-2024-27884
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 with a new entitlement. This issue is fixed in iOS 17.5 and iPadOS 17.5, macOS Sonoma 14.5, tvOS 17.5, visionOS 1.2, watchOS 10.5. An app may be able to access user-sensitive data.
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 confidenceA vulnerability in multiple Apple operating systems allowed an application to access user-sensitive data. The issue was addressed by implementing a new entitlement to restrict such access. The vulnerability affects iOS 17.5, iPadOS 17.5, macOS Sonoma 14.5, tvOS 17.5, visionOS 1.2, and watchOS 10.5.
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.5< 17.5< 14.5< 10.5< 1.2< 17.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 versionGo to Settings > General > About > Version on the iPhone or iPadAffected if Version is lower than 17.5 (for example, 17.4 or earlier)
-
Check iPadOS versionGo to Settings > General > About > Version on the iPadAffected if Version is lower than 17.5 (for example, 17.4 or earlier)
-
Check macOS versionClick the Apple menu > About This Mac, or run 'sw_vers' in TerminalAffected if Version is lower than 14.5 (for example, 14.4 or earlier)
-
Check watchOS versionOpen the Watch app on iPhone > My Watch > General > About > VersionAffected if Version is lower than 10.5 (for example, 10.4 or earlier)
-
Check tvOS versionGo to Settings > General > About > Version on Apple TVAffected if Version is lower than 17.5 (for example, 17.4 or earlier)
-
Check visionOS versionGo to Settings > General > About > Version on Apple Vision ProAffected if Version is lower than 1.2 (for example, 1.1 or earlier)
You are affected if any of your Apple devices (iPhone, iPad, Mac, Apple Watch, Apple TV, or Vision Pro) are running an OS version lower than the corresponding fixed version (iOS/iPadOS/tvOS 17.5, macOS 14.5, watchOS 10.5, visionOS 1.2).
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.514.5
Update all affected devices to the fixed OS versions (iOS 17.5/iPadOS 17.5, macOS Sonoma 14.5, tvOS 17.5, visionOS 1.2, watchOS 10.5) to apply the new entitlement restrictions.
iOS 17.5, iPadOS 17.5, macOS 14.5 (Sonoma), tvOS 17.5, watchOS 10.5, visionOS 1.2
- Upgrade iPhone or iPad to iOS 17.5 or iPadOS 17.5 respectively
- Upgrade macOS devices to macOS Sonoma 14.5
- Upgrade Apple TV devices to tvOS 17.5
- Upgrade Apple Watch devices to watchOS 10.5
- Upgrade Apple Vision Pro devices to visionOS 1.2
- After upgrading, verify the new entitlement is active by checking system integrity
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27884 — 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-2024-27884 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