dbcve.org
IpadosOperating system · Apple

CVE-2024-23223

MEDIUM · 6.2 CVSS v3.1 Published 2024-01-23
Fix available
A fix is available. Upgrade to 10.3 / 14.3 or later.
See remediation →
67/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
A privacy issue was addressed with improved handling of files. This issue is fixed in iOS 17.3 and iPadOS 17.3, macOS Sonoma 14.3, tvOS 17.3, watchOS 10.3. An app may be able to access sensitive user 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 · low confidence

This is a privacy vulnerability in Apple's file handling implementation that allowed a malicious application to access sensitive user data. The vulnerability was addressed through improved file handling controls in iOS 17.3, iPadOS 17.3, macOS Sonoma 14.3, tvOS 17.3, and watchOS 10.3. The specific mechanism of exploitation and exact data categories affected are not detailed in the available advisory.

MitigationApply the vendor-supplied OS updates (iOS 17.3+, macOS Sonoma 14.3+, tvOS 17.3+, watchOS 10.3+) to affected devices to remediate this vulnerability.

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
IpadosOperating system
Affected:< 17.3
Iphone OsOperating system
Affected:< 17.3
macOSOperating system
Affected:>= 14.0, < 14.3
TvosOperating system
Affected:< 17.3
WatchosOperating system
Affected:< 10.3

CVSS 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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify your Apple device and operating system
    Determine whether the device runs iOS, iPadOS, macOS, tvOS, or watchOS. On iPhone/iPad, go to Settings > General > About. On Mac, go to Apple menu > About This Mac. On Apple TV, go to Settings > General > About. On Apple Watch, open the Watch app on iPhone and go to General > About.
    Affected if The device runs any of the affected Apple operating systems listed in the CVE.
  2. Check iOS or iPadOS version
    On iPhone or iPad, go to Settings > General > About and note the version number shown next to Software Version.
    Affected if The installed version is less than 17.3 (for example, 17.2.x, 17.1.x, or earlier).
  3. Check macOS version
    On Mac, go to Apple menu > About This Mac. The version number appears as e.g., 14.2, 14.1, or 14.0 next to macOS Sonoma.
    Affected if The installed version is 14.0, 14.1, or 14.2 (any version from 14.0 up to but not including 14.3).
  4. Check tvOS version
    On Apple TV, go to Settings > General > About and look for the version number next to tvOS.
    Affected if The installed version is less than 17.3.
  5. Check watchOS version
    On Apple Watch, go to Settings > General > About on the watch, or open the Watch app on paired iPhone and go to General > About.
    Affected if The installed version is less than 10.3.

If the device runs any affected Apple OS version below the fixed release (iOS 17.3, iPadOS 17.3, macOS 14.3, tvOS 17.3, or watchOS 10.3), the environment is vulnerable to this file handling privacy flaw.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.3 / 14.3 / 17.3 or later
Fixed in 10.314.317.3
Interim mitigation

Apply the vendor-supplied OS updates (iOS 17.3+, macOS Sonoma 14.3+, tvOS 17.3+, watchOS 10.3+) to affected devices to remediate this vulnerability.

Recommended fix High confidence

iOS 17.3 and iPadOS 17.3, macOS Sonoma 14.3, tvOS 17.3, watchOS 10.3

  1. Check the current iOS/iPadOS version by going to Settings > General > About
  2. Check the current macOS version by clicking the Apple menu > About This Mac
  3. Check the current tvOS version by going to Settings > General > About
  4. Check the current watchOS version by opening the Watch app on iPhone > General > About
  5. For iPhone/iPad: Go to Settings > General > Software Update and update to iOS/iPadOS 17.3
  6. For Mac: Go to System Settings > General > Software Update and update to macOS Sonoma 14.3
  7. For Apple TV: Go to Settings > General > Software Update and update to tvOS 17.3
  8. For Apple Watch: On the iPhone, open the Watch app > General > Software Update and update to watchOS 10.3
Caveat Standard minor update risk; always backup before updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ipados Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23223 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-23223 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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