IpadosOperating system · Apple

CVE-2024-23215

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

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
An issue was addressed with improved handling of temporary 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 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 · high confidence

A vulnerability in Apple's iOS, iPadOS, macOS, tvOS, and watchOS allows a malicious local application to access sensitive user data due to improper handling of temporary files. The flaw enables an app to potentially read data outside its intended sandbox boundaries.

MitigationApply vendor updates: iOS 17.3+, iPadOS 17.3+, macOS Sonoma 14.3+, tvOS 17.3+, and watchOS 10.3+. No further technical remediation is available for older versions.

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Check iOS version
    Go to Settings > General > About on the iPhone or iPad. Note the version number displayed.
    Affected if The version is less than 17.3 (for example, 17.2, 17.1, 16.x, etc.)
  2. Check iPadOS version
    Go to Settings > General > About on the iPad. Note the version number displayed.
    Affected if The version is less than 17.3 (for example, 17.2, 17.1, 16.x, etc.)
  3. Check macOS version
    Click the Apple menu > About This Mac. Note the version number (for example, 14.0, 14.1, 14.2).
    Affected if The version is 14.0, 14.1, or 14.2 (Sonoma releases before 14.3). Versions 14.3+ and 13.x are not affected.
  4. Check tvOS version
    Go to Settings > General > About > Version on Apple TV.
    Affected if The version is less than 17.3 (for example, 17.2, 17.1, etc.)
  5. Check watchOS version
    Open the Watch app on iPhone, go to My Watch > General > About, or on Apple Watch go to Settings > General > About.
    Affected if The version is less than 10.3 (for example, 10.2, 10.1, etc.)

Your device is affected if it runs iOS, iPadOS, tvOS, or watchOS before 17.3, or macOS Sonoma between 14.0 and 14.2, and a malicious app with the ability to create and access temporary files is installed on the device.

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 vendor updates: iOS 17.3+, iPadOS 17.3+, macOS Sonoma 14.3+, tvOS 17.3+, and watchOS 10.3+. No further technical remediation is available for older versions.

Recommended fix High confidence

iOS 17.3 / iPadOS 17.3 / macOS Sonoma 14.3 / tvOS 17.3 / watchOS 10.3

  1. Identify the affected Apple device (iPhone, iPad, Mac, Apple TV, or Apple Watch)
  2. Ensure the device is connected to power and backed up to iCloud or local storage
  3. For iPhone/iPad: Go to Settings > General > Software Update and install iOS 17.3 or iPadOS 17.3
  4. For Mac: Go to System Settings > General > Software Update and install macOS Sonoma 14.3
  5. For Apple TV: Go to Settings > System > Software Updates and install tvOS 17.3
  6. For Apple Watch: On iPhone, open the Watch app, go to General > Software Update and install watchOS 10.3
Caveat Standard OS update risks apply (brief downtime, ensure backup before updating)

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23215 — 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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-23215 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