CVE-2024-54564
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 through improved state management. This issue is fixed in iOS 17.6 and iPadOS 17.6, macOS Sonoma 14.6, visionOS 1.3. A file received from AirDrop may not have the quarantine flag applied.
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 confidenceFiles received via AirDrop bypass the quarantine flag, allowing them to execute without Gatekeeper security warnings. This means malicious files can run without the normal user prompts that warn about potentially unsafe code.
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< 17.6< 14.6< 1.3CVSS 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
- Low
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
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 or iPadOS versionOpen Settings > General > About and note the version number displayed (e.g., 17.5, 17.5.1)Affected if The version is below 17.6 (e.g., 17.5, 17.5.1)
-
Check macOS versionClick the Apple menu > About This Mac, or run 'sw_vers -productVersion' in TerminalAffected if The version is below 14.6 (e.g., 14.5, 14.5.1)
-
Check visionOS versionOpen Settings > General > About and note the version numberAffected if The version is below 1.3 (e.g., 1.2, 1.2.1)
-
Determine if AirDrop has been usedCheck your Downloads folder, Desktop, or recent file locations for files received via AirDrop. On macOS, you can also run 'ls -l@ ~/Downloads' to see file attributesAffected if Files received via AirDrop exist on the device and the OS version is vulnerable
You are affected if your device runs iOS/iPadOS below 17.6, macOS below 14.6, or visionOS below 1.3 AND you have received files through AirDrop, as those files may have bypassed quarantine and run without Gatekeeper warnings.
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.314.617.6
Apply the vendor-supplied updates: iOS 17.6, iPadOS 17.6, macOS Sonoma 14.6, or visionOS 1.3.
iOS 17.6, iPadOS 17.6, macOS Sonoma 14.6, visionOS 1.3
- For iPhone: Go to Settings > General > Software Update and update to iOS 17.6
- For iPad: Go to Settings > General > Software Update and update to iPadOS 17.6
- For Mac: Go to System Settings > Software Update and update to macOS Sonoma 14.6
- For Vision Pro: Go to Settings > General > Software Update and update to visionOS 1.3
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-54564 — 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-54564 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